public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc
Date: Sun, 8 Jun 2008 19:09:34 -0300	[thread overview]
Message-ID: <20080608220934.GA22242@ime.usp.br> (raw)
In-Reply-To: <200806090002.17938.IvDoorn@gmail.com>

Hi, Ivo.

Thank you very much for your very kind reply.

On Jun 09 2008, Ivo van Doorn wrote:
> Hi,
> 
> > Nice to know that. I saw that the code has changed quite a good
> > amount...
> 
> Hehe, yes rt2x00 code is moving quit a lot per kernel release.

Granted. :-) You have been working quite a lot. :-)

> > Anyway, I don't know if you saw the various outputs that I put at my
> > homepage (lots of dmesgs with the 2.6.26-rc4 kernel):
> > http://www.ime.usp.br/~rbrito/debug/
> 
> Yeah, saw them.

Hope that they prove somewhat useful.

> > > > I don't know if the firmware is needed in my case or not, though (my USB
> > > > adaptor is a D-Link DWL-G122 H/W Ver. B1, F/W Ver.: 2.03---took that info
> > > > from the back of the stick).
> > > 
> > > Which driver is actually being used? rt2500usb or rt73usb?
> > 
> > The driver that actually gets loaded is rt2500usb. I tried rmmod'ing
> > rt2500usb and loading rt73usb, but a quick iwconfig doesn't even show
> > the interfaces.
> 
> That means it really is a rt2500usb device. ;)

Yes. :) I have firmware files installed under /lib/firmware also (taken
from Debian's unstable release---which is what I am using). Are they
needed?

> > > Also what was the last kernel version on which the driver worked for
> > > you?
> > 
> > Unfortunately, I don't have any kernel for which this has worked for
> > me. I just did an experiment: I plugged the adaptor on a ia32
> > notebook where a rt61pci works fine (it is running Ubuntu's
> > Hardy---well, actually, there are some problems, but I can get to
> > that latter), but the USB key was non working with the symptoms that
> > I described above.
> 
> That is most unfortunate, since register dumps are usually most usefull when
> I can compare the actual register values between a working and
> non-working setup.

Ok. I will try to compile an 2.6.18 kernel with the out-of-tree modules.
I hope that this can prove useful. I plan on getting register dumps (and
I also hope that it will work; perhaps getting the register values with
the legacy rt2500 drivers would help you, if they are available at all.
I don't even know if they will work here, but I guess that I will give
them a shot).

> However I just realized I had a D-Link stick myself, and apparently I have the exact
> same model/type. I'll compile a 2.6.26-rc5 kernel and see if that stick works for me,
> if so, I have the working register dump. And if not, then we can rule
> out endian problems.

Thank you so much.

I will compile other versions of the kernel just to see if I can see the
status of the driver with other versions of kernels/drivers. Since I
just installed a cross-compiler yesterday night on a *much* faster
machine, I don't have to wait more than 1 hour for each kernel
modification that I make (this iBook is slow).

As I said earlier, I plan on doing whatever test you want me to.


Thanks, Rogério Brito.

-- 
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org

  reply	other threads:[~2008-06-08 22:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 19:30 [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc Rogério Brito
2008-06-01 22:58 ` Rogério Brito
2008-06-06 16:23 ` John W. Linville
2008-06-07  0:52   ` Rog?rio Brito
2008-06-07 14:30     ` John W. Linville
2008-06-08  0:11       ` Rogério Brito
2008-06-08  1:02         ` Rogério Brito
2008-06-08 10:42           ` Ivo van Doorn
2008-06-08 21:35             ` Rogério Brito
2008-06-08 22:02               ` Ivo van Doorn
2008-06-08 22:09                 ` Rogério Brito [this message]
2008-06-08 22:30                   ` Rogério Brito
2008-06-09  0:15                 ` Rogério Brito
2008-06-11  9:36                   ` Rogério Brito
2008-06-11 13:43                     ` John W. Linville
2008-06-12  4:15                       ` Rogério Brito
2008-06-11 18:21                     ` Ivo van Doorn
2008-06-12  4:23                       ` Rogério Brito
2008-06-12 17:40                         ` Ivo van Doorn
2008-06-13  4:06                           ` Rogério Brito
2008-06-13  4:52                             ` Rogério Brito
  -- strict thread matches above, loose matches on Subject: below --
2008-06-20 17:57 [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd) Rogério Brito
2008-06-20 19:58 ` Rogério Brito
2008-06-25 19:49   ` Rogério Brito
2008-08-04 13:26     ` Ivo van Doorn
2008-08-07 17:01       ` [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc Rogério Brito

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080608220934.GA22242@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox