On Tue, 19 Jun 2007, Christopher Friedt wrote:
> Triffid Hunter wrote:
>> gentoo's crossdev tool and tinygentoo and lvm2 root (initramfs) howtos
>> were really helpful too although by now I've made enough initramfs' to set
>> up the system root without problems.. you may notice that my current
>> 2.6.21 is a gentoo kernel ;)
>
> I'm using gentoo's crossdev as well, but more closer to the 2.6.20
> series vanilla kernels from kernel.org. Did you have to patch the gentoo
> 2.6.21 kernel with anything except the few mentioned before?
Nope, same patch set although some of the hunks fail for some reason -
applying them manually and re-diffing gives no visual difference which is
strange.. must be a whitespace thing.
> We should really post a few patches to a vanilla kernel on the ts7000
> yahoo groups site, so that people can easily find what they need. Even
> posting a small document on that site containing instructions to apply
> the patches would certainly be helpful.
This would be extremely helpful I think :)
> Initramfs is an awesome thing, but I haven't really used it extensively
> with the TS boards. I've used initramfs when I started playing around
> with Qemu, only for demo purposes, but I think that it's a very valuable
> tool for setting up modules before handing everything over to userspace.
I'm not using initramfs or modules at the moment.. kernel has module
support but everything I need is built in. My theory on initramfs's is
that they should only be used when it's impossible to mount / without
running a program first.
> These days I'm trying to use Qemu more for building packages for the TS
> boards, and it works like a charm with a gentoo embedded stage3
> filesystem for the arm - the only downside is that the processor is
> slightly different (926 instead of 920) - I'll hopefully put together
> some info on how others can do this too
>
> <tangential>
> - actually, it would be ___AMAZING___ if TS could port some of their
> system components so that we could do simulations with Qemu (hint
> hint!!), and I'm sure that it would likely help sales when people find
> out they could quickly simulate things on their workstation without
> having to upload and run / power down every time.
> </tangential>
>
> Could you perhaps write out a few steps for your initramfs image to
> share with everyone else? Do you know if it's possible to build it
> separately as an 'initrd' style image, or do you need to build it in
> directly to the kernel?
I don't use one - I boot directly from either nfs or flash. However, I've
made numerous initramfs' for x86 machines, and gentoo's tinygentoo and
lvm2 on raid howtos excellent for that.
In those environments, I simply point the kernel to the directory where
the relevant files are and it looks after the rest for me. I was reading
redboot instructions the other day, looks like it supports loading initrd
images but I expect it'll still be easier to build it in.
> Could you post your busybox configs / uClibc configs?
busybox:
http://triffid.funkmunch.net/console-tools/busybox-1.4.1-r2.config
kernel:
http://triffid.funkmunch.net/console-tools/ts7250-linux-config-2.6.21
I'm using glibc rather than uClibc - I want to play with threads and not
sure how uClibc's performance is with those. glibc doesn't take up too
much space :-
ts7250 ~ $ uname -a
Linux ts7250 2.6.21-gentoo-ts7250 #4 PREEMPT Sun Jun 17 23:40:13 EST 2007
armv4tl unknown
ts7250 ~ $ df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 125.0M 20.4M 104.6M 16% /
devtmp 30.0M 0 30.0M 0% /dev
shm 30.0M 0 30.0M 0% /dev/shm
tmp 30.0M 0 30.0M 0% /tmp
I may change when I start using the new eabi, so pros and cons are welcome
:)
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|