-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El Tue, 3 Jul 2012 15:13:09 +0100 "Richard W.M. Jones"<rjones(a)redhat.com> escribió: > > I know we don't support tablets. That's been pretty comprehensively > covered on the list already, eg: > > https://lists.fedoraproject.org/pipermail/arm/2012-April/003107.html > > But! Suddenly a tablet appears which is both much cheaper and (in > some respects) far more powerful than the Trim Slices and BeagleBoards > that we do support. > > Is it possible to support Tegra2/3 tablets, at least in a headless > configuration until there are graphics drivers? > > Rich. > It should be doable, aboot that android devices use is different to uboot. on my ac100 ive had troubles getting an initrd loaded. i get errors about the initramfs being corrupted.

its also space constrained so you have to make a host specific initramfs to fit in the 8mb limits it places on kernel and initramfs.

you could possibly also just use the android kernel though im not sure if that is sufficient. I know KDE has been working on a touch interface, pretty sure gnome has also. I do expect at some point soon we will see tablet spins show up for arm and x86.

On 07/03/2012 03:13 PM, Richard W.M. Jones wrote: > > > I know we don't support tablets. That's been pretty comprehensively > covered on the list already, eg: > > https://lists.fedoraproject.org/pipermail/arm/2012-April/003107.html > > But! Suddenly a tablet appears which is both much cheaper and (in > some respects) far more powerful than the Trim Slices and BeagleBoards > that we do support. > > Is it possible to support Tegra2/3 tablets, at least in a headless > configuration until there are graphics drivers? Is there any particular reason why you cannot do something like: 1) root the device 2) dump the rootfs in a subdirectory 3) chroot /sbin/init ? Assuming you enabled sshd, you should at that point be able to ssh into the tablet. Or is there something in the Android kernel patches that stops this approach?

I know we don't support tablets. That's been pretty comprehensively covered on the list already, eg: https://lists.fedoraproject.org/pipermail/arm/2012-April/003107.html

But! Suddenly a tablet appears which is both much cheaper and (in some respects) far more powerful than the Trim Slices and BeagleBoards that we do support. Is it possible to support Tegra2/3 tablets, at least in a headless configuration until there are graphics drivers?

On 07/03/2012 03:32 PM, Peter Robinson wrote: > > On Tue, Jul 3, 2012 at 3:13 PM, Richard W.M. Jones<rjones(a)redhat.com> > wrote: >> >> >> I know we don't support tablets. That's been pretty comprehensively >> covered on the list already, eg: >> >> https://lists.fedoraproject.org/pipermail/arm/2012-April/003107.html > > > Actually that doesn't state we don't comprehensively want to support > tablets, it states at the moment it's hard to support tablets. I would > love to be able to support tablets and the touch stuff is improving > all the time, like with F-17 we actually now have the underlying > support for multitouch, now if only we had some even half decent X > drivers we'd be well on the way there. There's even people working on > the gnome touch stuff on ARM so it should improve even more in the > F-18 cycle! > >> But! Suddenly a tablet appears which is both much cheaper and (in >> some respects) far more powerful than the Trim Slices and BeagleBoards >> that we do support. >> >> Is it possible to support Tegra2/3 tablets, at least in a headless >> configuration until there are graphics drivers? > > > It's possible if the relevant kernel code is upstream. I've got one on > order with the intention of looking at what would be required to make > it work and to hack around with it. With 3.4 the beginnings of the > tegra30 support started to appear. I'm hoping google is a lot better > at pushing it upstream than say Toshiba with the AC100. This is another part that is really perverse - it shouldn't be Google/Toshiba pushing Tegra support upstream, it should be Nvidia.