It is a Marvell Chipset.
Jimmy Pierce
[EMAIL PROTECTED]
Jamie Painter wrote:
David Hollis wrote:
Ok, I have a Buffalo engineering sample that is using a Marvell PHY. Do
you know what kind of PHY the Airlink has?
I don't know, and haven't been willing t
David Hollis wrote:
Ok, I have a Buffalo engineering sample that is using a Marvell PHY. Do
you know what kind of PHY the Airlink has?
I don't know, and haven't been willing to pry one open to see if I can
figure it out. The gpio/PHY handling I did was largely trial and error
based on wh
On Thu, 2005-08-11 at 13:44 -0600, Jamie Painter wrote:
> David Hollis wrote:
> Sounds good. I'll send you what I have once I've made a pass over it
> to clean it up.
>
> My initialization and PHY handling is limited to supporting the one
> device I had to test with:
> airlink-101 AGIGUSB: ht
Hi all,
Not sure where to post this, so please redirect me if this isn't the place.
I'm having some problems with my USB2 NIC, DLink DUB-E100. According to the
specs it should be able to run 100mbit FDX on High-speed USB 2.0.
It's also listed on http://www.linux-usb.org/usbnet/ as a supported ad
Greg:
This patch (as556) adds support for unbinding the usb_generic "driver".
That driver only binds to USB devices, as opposed to interfaces, and it
does nothing much besides marking which struct device's go with an
overall USB device plus providing suspend/resume methods. Now that users
can u
David Hollis wrote:
I'm the current maintainer of the ASIX code in usbnet. I've spent some
time working with ASIX on a driver for the AX88178 device, but it hasn't
gotten to a stable point worth merging at this time. Let's work
together to get this code fixed up so that we can have a stable dr
On Thu, Aug 11, 2005 at 03:27:53PM -0400, Alan Stern wrote:
>
> If you like the patch, I'll resend it with a real Changelog message.
I like it, care to resend?
thanks,
greg k-h
---
SF.Net email is Sponsored by the Better Software Conference
On Thu, 11 Aug 2005, Greg KH wrote:
> > Well, there's still a little bit to discuss. Pat mentioned that in
> > general, the remove method is supposed to handle children. Presumably
> > this applies to the usb_generic driver. Should it try to unconfigure a
> > USB device (thus deleting the inter
On Thu, Aug 11, 2005 at 11:26:35AM -0400, Alan Stern wrote:
> On Wed, 10 Aug 2005, Greg KH wrote:
>
> > On Mon, Aug 08, 2005 at 03:59:56PM -0400, Alan Stern wrote:
> > > On Mon, 8 Aug 2005, Patrick Mochel wrote:
> > > > On Sat, 6 Aug 2005, Alan Stern wrote:
> > > > > There probably are situations
On Wed, 2005-08-10 at 23:07 -0600, James Painter wrote:
> For what it is worth, I have working AX88178 code for the usbnet driver
> I've been trying to find time to polish up to submit. I've been using
> it daily for several months in a backport to 2.4 for an embedded system
> (tivo). It's ha
On Thu, 11 Aug 2005, Juergen Schindele wrote:
> Am Mittwoch, 10. August 2005 16:48 schrieb Alan Stern:
> First thanks for your reply .
>
> > The driver doesn't utilize this buffer as much as it could. It should set
> > touchkit->irq->transfer_dma to touchkit->data_dma and
> > touchkit->irq->tran
On Wed, 10 Aug 2005, Greg KH wrote:
> On Mon, Aug 08, 2005 at 03:59:56PM -0400, Alan Stern wrote:
> > On Mon, 8 Aug 2005, Patrick Mochel wrote:
> > > On Sat, 6 Aug 2005, Alan Stern wrote:
> > > > There probably are situations where this doesn't matter. But in
> > > > general,
> > > > don't you t
On Thu, 11 Aug 2005, wu harry wrote:
> > 2.4.24 is pretty old. If at all possible, you
> > should work with a current
> > 2.6 kernel.
> >
> > This is a pretty obvious point... but if you want
> > help debugging a
> > USB problem, the best way to start is to turn on the
> > kernel's USB
> > debu
Greg:
This patch (as555) modifies the already-awkward usb_lock_device_for_reset
routine in usbcore by adding a timeout. The whole point of the routine
is that the caller wants to acquire some semaphores in the wrong order;
protecting against the possibility of deadlock by timing out seems only
On 11/08/2005 09:30, Uwe Bonnes wrote:
at the moment (2.6.13-rc4) ftdi_chars_in_buffer() unconditionally return
0. Shouldn't this function at least check the FTDI_RS_TEMT bit in Byte1
(Line Status)?
I don't think so, but it shouldn't really return zero until all write
URBs currently in-fligh
hi,
I have a USB bridge with chipset PL2501 which is not
supported by usbnet.
vandor id 0x067b (prolific) product id =0x2501
What changes do i have to do ; to make it get
recognised?
are any patches or fixes available for the same ?
Regards
:-)
__
Hello,
I have a device not listed in "usb.ids":
---8<---
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 18 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=1004 ProdID=6005 Rev= 1.00
S: Manufacturer=LG Electronicst
S: Product=LG Mobile Agent
C:* #
Hallo,
at the moment (2.6.13-rc4) ftdi_chars_in_buffer() unconditionally return
0. Shouldn't this function at least check the FTDI_RS_TEMT bit in Byte1
(Line Status)?
Cheers
--
Uwe Bonnes[EMAIL PROTECTED]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
-
Hi All,
I am wondering if there are any on going efforts to implement USB OTG
standard on Linux. I am currently looking at writing the USB OTG drivers for
the TI DM320 processor. Any patches related to OTG support for Linux
available? I read somewhere that partial support is available but hasn
On Wed, Aug 10, 2005 at 10:49:19PM -0700, Randy.Dunlap wrote:
> On Wed, 10 Aug 2005 21:58:46 -0700 Greg KH wrote:
>
> >
> > > + while(!test_bit(AX88178_UNPLUG, &dev->flags) )
> > > + {
> >
> > Please use the proper formatting for your braces. Same thing for your
> > if statements.
> >
> > Also
Am Mittwoch, 10. August 2005 16:48 schrieb Alan Stern:
First thanks for your reply .
> The driver doesn't utilize this buffer as much as it could. It should set
> touchkit->irq->transfer_dma to touchkit->data_dma and
> touchkit->irq->transfer_flags to URB_NO_TRANSFER_DMA_MAP. However, even
> wit
Greg: huge thanks for the detailed critique!
Jimmy: let me know if you need/want any help with review
and/or patch construction and shipping. :-)
Bart
In message <[EMAIL PROTECTED]> you wrote:
> On Wed, Aug 10, 2005 at 04:50:35PM -0700, [EMAIL PROTECTED] wrote:
> > +typedef struct ax8817
22 matches
Mail list logo
