From: Sriranga Veeraraghavan <ranga@CSUA.Berkeley.EDU>
To: linuxppc-dev@lists.linuxppc.org
Subject: USB under LinuxPPC
Date: Tue, 04 May 1999 15:20:37 -0700 [thread overview]
Message-ID: <199905042220.PAA17423@soda.CSUA.Berkeley.EDU> (raw)
Hi,
I have been trying to compile USB support into the 2.2.5 kernel on
LinuxPPC using the uusb driver.
On my LinuxPPC machine I keep getting errors that the struct s_snode
has no element named lock. I checked in usb-slist.h and this struct's
definition does not have an element named lock, nevertheless it is
referenced throughout the usb driver code.
If anyone has been able to comple the uusb driver on LinuxPPC, I would
appreciate some pointers. Also if there is a version of the usb
drivers that compiles with kernel 2.2.0pre6, I would like to use it,
since the SMP support on 2.2.1+ has been quite buggy for me.
Thanks,
----ranga <ranga@soda.berkeley.edu>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-05-04 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-04 22:20 Sriranga Veeraraghavan [this message]
1999-05-05 0:05 ` USB under LinuxPPC Tom Rini
1999-05-05 5:55 ` Sriranga Veeraraghavan
1999-05-05 17:50 ` Tom Rini
1999-05-05 20:55 ` Derek Moeller
1999-05-05 0:06 ` Derek Moeller
1999-05-05 0:29 ` Paul Mackerras
[not found] <199905052108.QAA24980@cegt201.bradley.edu>
1999-05-06 1:32 ` Sriranga Veeraraghavan
1999-05-06 3:29 ` Brad Boyer
1999-05-06 19:17 ` Sriranga Veeraraghavan
1999-05-06 5:16 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
1999-06-30 18:45 Martin Costabel
1999-06-30 19:37 ` Tom Rini
1999-07-01 22:45 ` Martin Costabel
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=199905042220.PAA17423@soda.CSUA.Berkeley.EDU \
--to=ranga@csua.berkeley.edu \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).