00:48.59 | *** join/#elinux thraxisp (~thraxisp@24.139.16.154) |
03:51.39 | *** join/#elinux ashes (~ashes@modemcable247.172-202-24.mc.videotron.ca) |
04:03.22 | *** join/#elinux BennyFu (~BennyFu@173.81.134.188) |
04:03.52 | *** part/#elinux BennyFu (~BennyFu@173.81.134.188) |
08:52.25 | *** join/#elinux lyakh (~lyakh@p508986DA.dip0.t-ipconnect.de) |
09:45.27 | *** join/#elinux pb__ (~pb@blundell.swaffham-prior.co.uk) |
10:54.07 | *** join/#elinux pirho (debian-tor@gateway/tor-sasl/pirho) |
11:23.00 | *** join/#elinux Roland (~roland@195.50.208.35) |
11:45.20 | *** join/#elinux lyakh (~lyakh@p508986DA.dip0.t-ipconnect.de) |
13:28.26 | *** join/#elinux pirho (debian-tor@gateway/tor-sasl/pirho) |
13:52.48 | *** join/#elinux GPSFan (~kenm@64.92.145.112) |
16:11.58 | wmat | mnemoc: did you answer you're CONFIG_CMDLINE question? |
16:12.16 | wmat | if not, see http://cateee.net/lkddb/web-lkddb/CMDLINE.html |
16:32.14 | *** join/#elinux pirho (debian-tor@gateway/tor-sasl/pirho) |
16:52.13 | mnemoc | wmat: I can't get it working... :( I'm prepending vga=0x311 fine, but vesafb doesn't "get it" ... but when I append it from the bootloader it works |
16:52.16 | mnemoc | it's weird |
16:52.52 | mnemoc | can vesafb be reading it _before_ the get merged? |
16:53.40 | mnemoc | btw, x86 :) |
17:02.56 | wmat | mnemoc: try passing the decimal value vga=785 |
17:04.24 | wmat | see, http://wiki.antlinux.com/pmwiki.php?n=HowTos.VgaModes |
17:22.05 | mnemoc | wmat: the very same vga=0x.. works when passed from the bootloader, but i need the image to choose it's settings by itself, but i'll test |
17:45.03 | *** join/#elinux toi (~toi@d54C2AA76.access.telenet.be) |
18:28.44 | mnemoc | wmat: http://dpaste.com/274851/ :( |
18:30.31 | mnemoc | the timming difference is also interesting |
18:48.34 | *** join/#elinux russ_ (foobar@ip70-176-251-1.ph.ph.cox.net) |
19:09.17 | *** join/#elinux Russ (foobar@ip70-176-251-1.ph.ph.cox.net) |
19:09.17 | *** mode/#elinux [+o Russ] by ChanServ |
19:12.49 | *** join/#elinux speakman (~daniel@unaffiliated/speakman) |
19:18.57 | speakman | Any links on how to structure the file system on embedded devices? I used to have two partitions; one read-only for all software, and one writable for saving local data and preferences. But that seems like a pretty old solution these days. How does Android and other embedded system do it? And how do they handle the "factory reset" feature? |
19:23.47 | Russ | I dunno, /tmp and /dev are pretty much always tmpfs |
19:23.57 | Russ | / is usually ro |
19:24.22 | Russ | /var is a good canidate for a rw partition that can be wiped for "factory reset" |
19:27.08 | mnemoc | speakman: http://dpaste.com/274864/ <--- android's mess |
19:29.01 | speakman | I'm thinking of using UnionFS to mount a RW-partition on top of the "firmware" RO root fs. |
19:29.28 | speakman | Then the RW partition could be erased when doing factory reset |
19:30.59 | speakman | mnemoc: a read only yaffs2-partition? |
19:36.34 | mnemoc | i'm a noob, but the fs choice depends on your storage media and even how much memory and cpu power you have. no magic bullet |
19:37.05 | mnemoc | http://elinux.org/File_Systems |
19:39.17 | mnemoc | speakman: http://dpaste.com/274866/ <--- androids / funky hierarchy |
19:41.02 | Russ | unionfs seems like a bad overcomplication |
19:41.52 | Russ | bind mounts can simplify things |
19:49.20 | speakman | Russ: Good point! |
19:50.27 | speakman | I see Android symlinks its /etc... that could be done with a bind mount right? |
22:08.11 | *** join/#elinux uchobby (~uchobby01@76.233.37.237) |
22:36.54 | *** join/#elinux uchobby (~uchobby01@76.233.37.237) |