From: Ted Wood <ted@fgh.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] CANBUs Quesetion
Date: Tue, 15 Jan 2013 10:58:39 -0000 [thread overview]
Message-ID: <002d01cdf30f$46f45890$d4dd09b0$@co.uk> (raw)
In-Reply-To: <20130114195101.12914c2d@skate>
> >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.
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.
next prev parent reply other threads:[~2013-01-15 10:58 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 [this message]
2013-01-15 11:12 ` Patrick
2013-01-15 13:15 ` Stephan Hoffmann
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='002d01cdf30f$46f45890$d4dd09b0$@co.uk' \
--to=ted@fgh.co.uk \
--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