From: Greg KH <greg@kroah.com>
To: dongzai007@sohu.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: vid&pid problems in usb_probe()
Date: Sat, 8 May 2004 19:16:52 -0700 [thread overview]
Message-ID: <20040509021652.GA11738@kroah.com> (raw)
In-Reply-To: <6918778.1084068239397.JavaMail.postfix@mx0.mail.sohu.com>
On Sun, May 09, 2004 at 10:03:54AM +0800, dongzai007@sohu.com wrote:
> Sorry, I forgot to tell you, I have copied all the header files in
> "linux2.4.18/include/linux" to "/usr/include/linux". I am sure that
> there is no difference between "linux2.4.18/include/linux" and "/usr/include/linux"
>
> I build this driver like this:
>
> #gcc -c usb.c
> #insmod -f usb.o //due to version dismatch, i should use -f
>
> then plug a usb device.
That is _not_ the proper way to build a kernel module. Please read the
Linux Device Drivers for examples of how to do this the correct way
(it's availble online for free.)
> Could you help me test this program? Do you have an usb device? You can write a program
> like this, and test if it can report the right vid & pid.
> I downloaded a new kernel 2.6.5, after i started with the new kernel, lots of modules
> can not be loaded, so i changed back to 2.4.18, then I found my X-windows can not
> start. Did this error have something to do with this unstablity?
Did you read the release notes about how to move to the 2.6 kernel? I
recommend using that one for development, as the USB interface is nicer,
and faster, and the build process is _vastly_ simpler.
Also, this belongs on the linux-usb-devel mailing list, not here.
greg k-h
next prev parent reply other threads:[~2004-05-09 2:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 2:03 vid&pid problems in usb_probe() dongzai007
2004-05-09 2:16 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-08 9:05 dongzai007
2004-05-08 17:25 ` Randy.Dunlap
2004-05-08 3:48 dongzai007
2004-05-08 4:45 ` Randy.Dunlap
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=20040509021652.GA11738@kroah.com \
--to=greg@kroah.com \
--cc=dongzai007@sohu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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.