From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: atngw100/target_skeleton atngw100/target etc...
Date: Sat, 18 Oct 2008 15:32:14 +0200 [thread overview]
Message-ID: <200810181532.15141.markus.heidelberg@web.de> (raw)
In-Reply-To: <20081018124742.CEE273C848@busybox.net>
jacmet at uclibc.org, 18.10.2008:
>
> Log:
> target/device/Atmel: add /sys to target skeletons
>
> Reported by John Schimandle
>
> Added:
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/sys/
> trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/sys/.empty
> trunk/buildroot/target/device/Atmel/atstk100x/target_skeleton/sys/
> trunk/buildroot/target/device/Atmel/atstk100x/target_skeleton/sys/.empty
> trunk/buildroot/target/device/Atmel/root/target_skeleton/sys/
> trunk/buildroot/target/device/Atmel/root/target_skeleton/sys/.empty
The AVR32 based boards atngw100 and atstk100x should have already worked,
though I've only used them with Atmel's Buildroot. They create this directory
from Atmel/{atngw100,atstk100x}/device_table.txt, but it isn't included in
Atmel/root/device_table.txt, so it didn't work for the ARM boards.
There are several directories in various device_table.txt files, not related
to device files and not all those need special file permissions.
Markus
next prev parent reply other threads:[~2008-10-18 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 12:47 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: atngw100/target_skeleton atngw100/target etc jacmet at uclibc.org
2008-10-18 13:32 ` Markus Heidelberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-21 1:34 ulf at uclibc.org
2007-08-27 12:38 ` Hans-Christian Egtvedt
2007-08-27 21:15 ` Bernhard Fischer
2007-08-27 21:40 ` [Buildroot] svn commit: trunk/buildroot/target/device/Atmel:atngw100/target_skeleton " Ulf Samuelsson
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=200810181532.15141.markus.heidelberg@web.de \
--to=markus.heidelberg@web.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 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.