| 1 |
It's nice to see a lot more OpenMoko / FreeRunner related messages |
| 2 |
showing up on this list. |
| 3 |
|
| 4 |
In that vain, and I know that there was some hesitation to do this at |
| 5 |
the beginning of the OpenMoko kernel branch, but ... |
| 6 |
|
| 7 |
maybe we should create a separate build for |
| 8 |
sys-kernel/openmoko-sources the kernel / git eclasses. It probably |
| 9 |
won't be necessary to keep any separate patches in the portage tree, |
| 10 |
everything would be fetchable from git, so the addition would be |
| 11 |
fairly easy to include in the Portage tree. |
| 12 |
|
| 13 |
Has someone already done this? |
| 14 |
|
| 15 |
Until all of the changes make it back upstream, including it in the |
| 16 |
Portage tree would just simplify building it for non-openembedded |
| 17 |
users. Recently there has been a lot of talk on openmoko-devel about |
| 18 |
separating PCI from the DRM, which requires some modification at the |
| 19 |
kernel layer, aside from several modifications to Xorg. That being |
| 20 |
said, there is a lot more development happening in andy-tracking these |
| 21 |
days. |
| 22 |
|
| 23 |
C |
Archives