On Sat, Mar 8, 2014 at 5:11 AM, Peter TB Brett <peter@xxxxxxxxxxxxx> wrote: > On Sat, 8 Mar 2014 10:30:38 +0000, Peter Robinson <pbrobinson@xxxxxxxxx> > wrote: >>>> In the case of the Pandaboard ES B3, there is no known kernel able to >>>> boot the board. >>>> >>>> In the case of the A6, the upstream kernel is believed to support the >>>> board with a very recent version of uboot. However, recently one of our >>>> contractors (*not* an expert on ARM kernel & boot issues) was unable to >>>> find any Linux distribution that could boot on it. >>> >>> I think we need to make a distinction here between "kernel" and >>> "distribution". If you can boot a kernel, you can boot any distro's >>> rootfs >>> (I'm completely ignoring installers here). >> >> That's not entirely true, Fedora for example has a hard requirement on >> a number of kernel features that will cause major issues if they're >> not present. >> >> That said I honestly don't believe it should be too hard for someone >> with a hard debugger and a bit of know how to work out what is wrong >> with the Fedora kernel on the PandaBoard devices to allow them to be >> supported again in the main distribution kernel. The main problem >> we've got is people with the know how don't have the interest and visa >> versa. I personally just don't have the time and gave my HW debugger >> away as a result. >> > > The reason that we were considering providing some funding was in hope of > overcoming the lack-of-interest barrier. > Last I looked at it for the newer ES boards memory. Just need to create a new dts file, limiting the emifX node to only one cs instead of the two currently used by panda common. The memory timing will have to also be copied from u-boot, and the emif driver may need to be verified to only recognize one cs line. Regards, -- Robert Nelson http://www.rcn-ee.com/ _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
