From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Wrong installation path?
Date: Sun, 02 Feb 2014 18:55:54 +0100 [thread overview]
Message-ID: <52EE86AA.2040609@mind.be> (raw)
In-Reply-To: <20140131111153.036fcfd5@skate>
On 31/01/14 11:11, Thomas Petazzoni wrote:
> Dear Marco Trapanese,
>
> On Fri, 31 Jan 2014 09:45:17 +0100, Marco Trapanese wrote:
[snip]
>
>> For example, the lirc documentation says I should find a /dev/lirc
>> device if I'm using udev.
>> But on my target (which has udev!) there is no such a device.
>
> Probably because your kernel configuration lacks the support for the
> proper kernel subsystem or kernel drivers.
>
>> Where should I look at? How to know if I missed something in the
>> buildroot/kernel configuration or just in the package (lirc)
>> configuration files?
Or because lirc should install a udev rule but the buildroot wrapper
doesn't install it correctly (seems like since it looks like it also
didn't get the init script right).
Regards,
Arnout
>
> The package (lirc) is independent from the presence of absence
> of /dev/lirc<X>. As long as /dev/lirc<X> is not visible, then your
> problem is a kernel configuration problem. Of course, make sure your
> kernel has CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT enabled, these are
> mandatory if you use Buildroot udev support. See
> http://buildroot.org/downloads/manual/manual.html#_dev_management for
> details.
>
> Best regards,
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2014-02-02 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 8:45 [Buildroot] Wrong installation path? Marco Trapanese
2014-01-31 10:11 ` Thomas Petazzoni
2014-02-02 17:55 ` Arnout Vandecappelle [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=52EE86AA.2040609@mind.be \
--to=arnout@mind.be \
--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