No, I didn't. Saw your notes regarding that and tried, however, my 5600 didn't recognize the ext3 partition when I made one on my SD card. Does it perhaps have to be on CF? I guess I'll try that.

1. I noted that your /dev is empty, should it be populated from my devices /dev?

2. this whole binder - can that just be insmodded in my 5600's /dev or does it need to be copied over to android-root/dev before i chroot?

3. custom kernel- are you using a kernel built with the benno diffs?

thanks,

andy

It doesn't matter whether you use SD or CF, both work as long as you use ext3

1. /dev is populated when running /init2. For the M5-RC1? release I didn't bother to build the binder code as a kernel module. Androidzaurus tried to do that, but said it didn't seem to work, so I didn't bother to try.3. No, I took the 2.6.23 vanilla kernel, the android 2.6.23 kernel sources and created new diffs.

It doesn't matter whether you use SD or CF, both work as long as you use ext3

1. /dev is populated when running /init2. For the M5-RC1? release I didn't bother to build the binder code as a kernel module. Androidzaurus tried to do that, but said it didn't seem to work, so I didn't bother to try.3. No, I took the 2.6.23 vanilla kernel, the android 2.6.23 kernel sources and created new diffs.

It doesn't matter whether you use SD or CF, both work as long as you use ext3

1. /dev is populated when running /init2. For the M5-RC1? release I didn't bother to build the binder code as a kernel module. Androidzaurus tried to do that, but said it didn't seem to work, so I didn't bother to try.3. No, I took the 2.6.23 vanilla kernel, the android 2.6.23 kernel sources and created new diffs.