From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] busybox_1.18.2.bb: slugos needs a modified version of usb.sh script
Date: Sun, 30 Jan 2011 17:18:33 -0600 [thread overview]
Message-ID: <4D45F1C9.1020802@mwester.net> (raw)
In-Reply-To: <4D3CB26F.7060905@mentor.com>
On 1/23/2011 4:57 PM, Tom Rini wrote:
> On 01/23/2011 11:27 AM, Khem Raj wrote:
>> On Fri, Jan 21, 2011 at 5:25 PM, Mike Westerhof<mike@mwester.net> wrote:
>>> Isn't this kernel-specific, though? I don't have any other OE-based
>>> devices handy just now to check, but what's difference, specifically,
>>> and should we change something to bring SlugOS into line with the rest
>>> of the world?
>>>
>>> -Mike (mwester)
>>>
>>
>> yes seems like slugos kernel enables.
>> CONFIG_SYSFS_DEPRECATED=y
>> CONFIG_SYSFS_DEPRECATED_V2=y
>>
>> which enabled these. I havent tested the kernel by disabling them
>> as I havent figured out how to boot a kernel from network on slug
>> but if you can try that and see what /sys/class looks like that
>> would help or if I find some time to make slug suck the kernel
>> from a tftp then I can do it too.
>
> Note that these kernel options also place an upper bound on what udev
> can be used and it's very much worth checking if they can be turned off.
SlugOS has bumped up to a 2.6.29 kernel with the above CONFIG items
disabled. (This is still a relatively old kernel, but I know that it
basically works with SlugOS, so it's a good place to test mdev and, if
anyone wants to, newer udevs.)
-Mike (mwester)
next prev parent reply other threads:[~2011-01-30 23:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 8:29 [PATCH 3/3] busybox_1.18.2.bb: slugos needs a modified version of usb.sh script Khem Raj
2011-01-21 8:58 ` Eric Bénard
2011-01-21 16:33 ` Khem Raj
2011-01-21 16:44 ` Eric Bénard
2011-01-21 18:07 ` Khem Raj
2011-01-22 1:25 ` Mike Westerhof
2011-01-23 18:27 ` Khem Raj
2011-01-23 22:57 ` Tom Rini
2011-01-30 23:18 ` Mike Westerhof [this message]
2011-01-24 9:03 ` Koen Kooi
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=4D45F1C9.1020802@mwester.net \
--to=mike@mwester.net \
--cc=openembedded-devel@lists.openembedded.org \
/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