On Wed, Jul 31, 2013 at 7:24 AM, Dave Jones <da...@redhat.com> wrote: > On Wed, Jul 31, 2013 at 10:40:12AM +0100, Russell King - ARM Linux wrote: > > On Tue, Jul 30, 2013 at 08:04:44PM -0400, Dave Jones wrote: > > > To use ARM as an example, the bugs I've seen have mostly been in arch > specific > > > code that does things like page-table manipulation. The chromebook bugs > I > > > was hitting for eg were various kinds of PTE corruption warnings. > > > > Hmm, really? Did you reported these bugs? I'm not aware of mainline > > having any changes related to bug reports on PTEs on ARM. > > I wasn't sure if it was a googleism, or happens on mainline, so no.
We'd definitely be interested in hearing about what you've found. The 3.4 kernel has a lot of out-of-tree code for exynos, we've reduced it quite a bit on the upcoming 3.8 one but it needs a bit more baking. As of 3.10, it's not actually hard to run a mainline kernel on the chromebook, but you have limited functionality (no wifi, no USB3, no accellerated graphics). Easiest is to do it by booting from SD card. See instructions at http://www.chromium.org/chromium-os/u-boot-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook. How long would a useful run of trinity take? I've got an autobuilder/autobooter setup here with a cross-section of current ARM hardware (7 platforms and counting) that I mostly do boot testing on, and I should add a smallish suite of testcases to the same. Trinity would be a good candidate for that. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
