From: Pavel Roskin <proski@gnu.org>
To: Fred Odendaal <freshshelf@rogers.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: at76_usb driver for WUSB11 v.26 wireless adapter doesn't work for kernels newer than 2.6.24.3-12.fc8
Date: Tue, 13 May 2008 23:51:05 -0400 [thread overview]
Message-ID: <1210737065.2721.8.camel@rd> (raw)
In-Reply-To: <482A5D2C.7020600@rogers.com>
On Tue, 2008-05-13 at 23:31 -0400, Fred Odendaal wrote:
> I installed Milan's patches (all 8 of them) and it's still broken. I
> realize that it's nice to have smaller patches for code reviews, but
> for testing it would be a lot easier to have one giant patch.
Actually, it would be great to have them in some git repository for wide
testing. But I want to take a look at the patches first.
> Is there anyway to get the driver to log messages as it's running? I
> noticed that "printk" is used a lot. Where would those messages go?
They go to the kernel log, which is shown by the dmesg command.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2008-05-14 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 1:03 at76_usb driver for WUSB11 v.26 wireless adapter doesn't work for kernels newer than 2.6.24.3-12.fc8 Fred Odendaal
2008-05-12 11:11 ` Pavel Roskin
2008-05-14 3:31 ` Fred Odendaal
2008-05-14 3:51 ` Pavel Roskin [this message]
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=1210737065.2721.8.camel@rd \
--to=proski@gnu.org \
--cc=freshshelf@rogers.com \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.