From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] CANBUs Quesetion
Date: Tue, 15 Jan 2013 14:15:56 +0100 [thread overview]
Message-ID: <50F5568C.8060007@relinux.de> (raw)
In-Reply-To: <002d01cdf30f$46f45890$d4dd09b0$@co.uk>
Am 15.01.2013 11:58, schrieb Ted Wood:
>>> How to do what? Sorry but your question is far from being precise
>>> enough to be understood.
> I'm really not sure how to make it any clearer than I did with my previous
> post. My response to Stephan Hoffman's suggestion that I integrate the
> driver into my kernel source and make a kernel patch out of it was to ask
> where I might find information on this. There is nothing in the Buildroot
> manual about it.
Ted,
kernel hackng is not a part of buildroot's scope.
I do not know about a good tutorial or so.
Maybe you want to read "Linux Device Drivers"
http://shop.oreilly.com/product/9780596005900.do and/or the information
provided on http://www.kernel.org/ and http://kernelnewbies.org/.
If you look at the driver's source code it should become clear. If it
does not you might want to think whether paying for commercial
assistance might be cheaper than learning it all.
You could also provide a link to the driver's source code, maybe someone
wants to have a look at it and give you the hints you need.
Stephan
>
> I'm not asking to be told how to do it, I'm asking for a pointer to where to
> find the information. As someone new to Embedded Linux I've been struggling
> to filter the huge volume of irrelevant and outdated material that Google
> throws up.
>
> But thank you for the guide to asking questions. I shall bear it in mind in
> future.
>
>
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
next prev parent reply other threads:[~2013-01-15 13:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 16:06 [Buildroot] CANBUs Quesetion Ted Wood
2013-01-11 16:14 ` Thomas Petazzoni
2013-01-11 16:16 ` Thomas Petazzoni
2013-01-14 11:26 ` Ted Wood
2013-01-14 11:36 ` Thomas Petazzoni
2013-01-14 11:45 ` Yegor Yefremov
2013-01-14 13:45 ` Stephan Hoffmann
2013-01-14 15:43 ` Ted Wood
2013-01-14 18:51 ` Thomas Petazzoni
2013-01-15 10:58 ` Ted Wood
2013-01-15 11:12 ` Patrick
2013-01-15 13:15 ` Stephan Hoffmann [this message]
2013-01-15 15:53 ` Ted Wood
2013-01-15 16:14 ` Thomas Petazzoni
[not found] ` <F3FEF4CEAF2D432EB1B98EB89DC2CBBF@beraninstruments.com.local>
2013-01-15 17:01 ` Thomas Petazzoni
2013-01-15 21:06 ` Yegor Yefremov
2013-01-15 13:36 ` Thomas Petazzoni
2013-01-15 15:14 ` Grant Edwards
2013-01-15 15:16 ` Grant Edwards
2013-01-15 15:39 ` Ted Wood
2013-01-15 15:38 ` Ted Wood
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=50F5568C.8060007@relinux.de \
--to=sho@relinux.de \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox