Fate of OMAP3-Touchbook board

Fate of OMAP3-Touchbook board

[Radek Pilar]

[-- Attachment #1.1: Type: text/plain, Size: 669 bytes --]

Hello,
a few months ago, Always Innovating - a company behind their OMAP3 based
product Touchbook basically stopped production. I've been porting some
specific drivers for current kernels since then and I'd like to push at
least some of them to the mainline.
However, I found  a bug in mainline that prevents this device from
booting - and looks like noone has reported it for a few months.
So, I'd like to ask - do you want to keep this board in mainline (in
this case, I can send a few patches adding few drivers (backlight,
accelerometer, soundcard, keyboard). Or do you want to remove it from
the mainline altogether?
Thanks for the answer
Radek Pilar

[-- Attachment #1.2: 0xE60DBF0D.asc --]
[-- Type: application/pgp-keys, Size: 6555 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

Re: Fate of OMAP3-Touchbook board

[Tony Lindgren]

* Radek Pilar <mrkva@mrkva.eu> [120815 14:00]:
> Hello,
> a few months ago, Always Innovating - a company behind their OMAP3 based
> product Touchbook basically stopped production. I've been porting some
> specific drivers for current kernels since then and I'd like to push at
> least some of them to the mainline.
> However, I found  a bug in mainline that prevents this device from
> booting - and looks like noone has reported it for a few months.
> So, I'd like to ask - do you want to keep this board in mainline (in
> this case, I can send a few patches adding few drivers (backlight,
> accelerometer, soundcard, keyboard). Or do you want to remove it from
> the mainline altogether?

The fix should be posted for -rc cycle. Minimal patches for the board-*.c
files are OK, but we should put most effort making things usable with
device tree based booting.

Regards,

Tony