[Arm-netbook] Framebuffer support - Mele A1000

[Alejandro Martínez]

If I'm not wrong, the framebuffer console was broken :(

I tried it on my tablet and it just didn't work (no screen output). I think
Tom tried it too and it didn't worked, and reported it to the girl who took
care of that part. Although given the Mele is a different device, it might
*just work*, but don't be surprised if it doesn't.

Also, there's no need at all to overwrite the default u-boot over adb. This
can be used: http://rhombus-tech.net/a10_mmc_boot/
A mksunxiboot bootable SD will just boot on any device (even bricked ones)
without any need to even touch the NAND.

Oh, and the device is rooted, so no problem with that :)


Alejandro

On Thu, Mar 22, 2012 at 9:54 PM, Peter Steenbergen <p.steenbergen at j1nx.nl>wrote:

> This is for one of the few people that already have the Mele A1000 device
> (I hope Tom puts me on the list for the second batch, so I can get a cheap
> and fast delivery for my own device).
>
> Looking at the Rhomtech hacking howto at;
> http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/
> You need to have the UART connection to have the u-boot and linux console.
> Can someone of you guys apply the following kernel tweak (make arch=arm
> menuconfig) and boot with that kernel
>
> Device Drivers -> Graphics support -> Console display driver support ->
> [*] Framebuffer Console support
> [*] Map the console to the primary display device (<- Optional, try the
> first one first)
>
> The above might re-route the linux console to the HDMI and/or VGA display
> device.
>
>
> Next steps would then be;
> 1) Make sure U-boot automatically boots from MMC when the proper
> files/partitions are in place at the card
> 2) Changing the default android install, such that it allows ADB over TCP
>
> setprop service.adb.tcp.port 5555
>
>
> stop adbd
> start adbd
>
> Or by using one of the "adb over wifi" apps. (Is the android firmware on
> the device rooted?)
>
>
> If we activated ADB over TCP and make sure we have an auto-boot mmc kind
> of u-boot ready. We can push the uboot image to the device over the network
> and the kernel will use framebuffer support to send the console to the
> normal display device.
>
> Then other people can just download the proper uboot image, push it to the
> device over TCP, and boot the kernels and linux variants without even
> opening up the device. No need for cables inside the device.
>
> But let's start with getting the console to the right place.
>
>
>
> _______________________________________________
> arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
> http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
> Send large attachments to arm-netbook at files.phcomp.co.uk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.phcomp.co.uk/pipermail/arm-netbook/attachments/20120322/ac9daf50/attachment-0001.html