David Hollis wrote:
Interesting, I wonder if anyone else is using these devices on other PPC
or like systems? I suppose they may be trying to use them but not
having much success and just not reporting it. I wouldn't be too
surprised if it's an endian issue, though the PHY handling has been a
On Fri, 2005-08-12 at 16:06 +0200, Magnus wrote:
> > David Hollis <[EMAIL PROTECTED]> wrote:
> > There were some fixes incorporated not too long ago that deal with the
> > speed negotiation, but those should already be incorporated into the
> > kernel you are running. It is possible that there a
> David Hollis <[EMAIL PROTECTED]> wrote:
> There were some fixes incorporated not too long ago that deal with the
> speed negotiation, but those should already be incorporated into the
> kernel you are running. It is possible that there are endian issues but
> I don't have any non-x86 hardware
On Fri, 12 Aug 2005, wu harry wrote:
> Thanks,Alan. I turned on these config items but did
> not find anything obviously wrong.May I have your
> suggestions? I post these module messages at boot up
> below. The USB device found there is a internally
> connected USB2.0 Card Reader.
>
> Thank you v
On Fri, 2005-08-12 at 03:02 +0200, Magnus wrote:
> Problem description:
> I can't set the NIC speed. It's fixed to 10 mbps, half-duplex, no matter
> what I do.
> I'm sure isn't tools reporting speed incorrectly, tests reveal speeds around
> 1mb/s (10mbit) on 100mbit net.
>
> I have tried both se
> 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
> >
Ian Abbott <[EMAIL PROTECTED]> wrote:
> 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 r
