So. I picked up a Linksys USB200M USB 2.0 ethernet adapter that uses
the ASIX Electronics AX88172 chip, and I started cobbling together a
driver. This chip uses a series of vendor specific commands to do
things like read/write the MII management interface on the MAC,
read/write the SROM, set the
On Fri, Mar 28, 2003 at 10:38:58AM -0800, Bill Paul wrote:
So. I picked up a Linksys USB200M USB 2.0 ethernet adapter that uses
the ASIX Electronics AX88172 chip, and I started cobbling together a
driver. This chip uses a series of vendor specific commands to do
things like read/write the
Just FYI
ng_ubt(4) (/sys/netgraph/bluetooth/drivers/ubt) driver
(Bluetooth USB devices) makes use of two interfaces.
thanks,
max
Bernd Walter wrote:
On Fri, Mar 28, 2003 at 10:38:58AM -0800, Bill Paul wrote:
So. I picked up a Linksys USB200M USB 2.0 ethernet adapter that uses
the ASIX
On Fri, Mar 28, 2003 at 11:16:55AM -0800, Maksim Yevmenkin wrote:
Just FYI
ng_ubt(4) (/sys/netgraph/bluetooth/drivers/ubt) driver
(Bluetooth USB devices) makes use of two interfaces.
From a look into the driver these interfaces serve different
protocols.
I asume they are unrelated from a
ng_ubt(4) (/sys/netgraph/bluetooth/drivers/ubt) driver
(Bluetooth USB devices) makes use of two interfaces.
From a look into the driver these interfaces serve different
protocols.
not sure what do you mean by protocol here. interface 0 has
control, interrupt, bulk-in and bulk-out endpoints.
On Fri, Mar 28, 2003 at 11:16:55AM -0800, Maksim Yevmenkin wrote:
Just FYI
ng_ubt(4) (/sys/netgraph/bluetooth/drivers/ubt) driver
(Bluetooth USB devices) makes use of two interfaces.
From a look into the driver these interfaces serve different
protocols.
I asume they are unrelated
On Fri, Mar 28, 2003 at 12:54:46PM -0800, Bill Paul wrote:
On Fri, Mar 28, 2003 at 11:16:55AM -0800, Maksim Yevmenkin wrote:
Just FYI
ng_ubt(4) (/sys/netgraph/bluetooth/drivers/ubt) driver
(Bluetooth USB devices) makes use of two interfaces.
From a look into the driver these
If memory serves me right, Tim Kientzle wrote:
The attached patch modifies the pkg_install
tools to inspect the file contents--rather than the
filename extension--to determine the
compression method in use. It then feeds the data
into the correct invocation of 'tar'.
I've also modified
Bernd Walter wrote:
Well the AC88172 PDF is very clear about having 2 interfaces.
The document also speaks about 4 endpoints, which I expect to be on
interface 0 as they also have listed endpoint number 0 - they don't
tell in the document.
What I currently don't know is why there are 2
Bruce A. Mah wrote:
If memory serves me right, Tim Kientzle wrote:
The attached patch modifies the pkg_install
tools to inspect the file contents--rather than the
filename extension--to determine the
compression method in use.
The concept is good, and it's something we've needed for awhile. I
Bruce A. Mah wrote:
The attached patch modifies the pkg_install
tools to inspect the file contents--rather than the
filename extension--to determine the
compression method in use.
... it works great for the case of a package coming in on stdin. If the
package comes from a file, ...
Oh, bloody
On Fri, Mar 28, 2003 at 10:47:43PM -0800, Tim Kientzle wrote:
P.S. It's galled me for a while that pkg_add has to fork 'tar' to
extract the archive. I've started piecing together a library that
reads/writes tarfiles. With this, it should be possible to make
pkg_add considerably more
12 matches
Mail list logo
