Looks like the missing kernel rpm is starting to cause troubles. I'm using common kernel and initramfs to provide support for the Kirkwood based devices like Sheevaplug or the QNAPs and thus need dracut to create the initramfs. And installing dracut now fails with
[root@fedora-arm ~]# LANG=C yum install dracut ... --> Running transaction check ---> Package libdrm.armv5tel 0:2.4.20-1.fc13 set to be updated --> Processing Dependency: kernel >= 2.6.29.1-52.fc11 for package: libdrm-2.4.20-1.fc13.armv5tel ---> Package sgpio.armv5tel 0:1.2.0.10-4.fc12 set to be updated --> Finished Dependency Resolution Error: Package: libdrm-2.4.20-1.fc13.armv5tel (fedora) Requires: kernel >= 2.6.29.1-52.fc11
So the options are - prepare a real kernel rpm (even when it shouldn't be much useful), prepare a fake kernel package (containing Provides: kernel=V-R only) or something else.
And I've chosen the fake the kernel method for now, see attachments.
Dan
Dan Horák wrote:
Looks like the missing kernel rpm is starting to cause troubles. I'm using common kernel and initramfs to provide support for the Kirkwood based devices like Sheevaplug or the QNAPs and thus need dracut to create the initramfs. And installing dracut now fails with
[root@fedora-arm ~]# LANG=C yum install dracut ... --> Running transaction check ---> Package libdrm.armv5tel 0:2.4.20-1.fc13 set to be updated --> Processing Dependency: kernel >= 2.6.29.1-52.fc11 for package: libdrm-2.4.20-1.fc13.armv5tel ---> Package sgpio.armv5tel 0:1.2.0.10-4.fc12 set to be updated --> Finished Dependency Resolution Error: Package: libdrm-2.4.20-1.fc13.armv5tel (fedora) Requires: kernel >= 2.6.29.1-52.fc11
So the options are - prepare a real kernel rpm (even when it shouldn't be much useful), prepare a fake kernel package (containing Provides: kernel=V-R only) or something else.
And I've chosen the fake the kernel method for now, see attachments.
I can see the fake dependency method is more generic, which is a good thing.
Standard kernels and bootloaders are something that will need to be looked at sooner or later, though. It might be an idea to start looking at what standard supported options might include. The most popular ones I can think of are (in no particular order):
SheevaPlugs (uboot, kirkwood) BeagleBoard/PandaBoard (uboot, OMAP) Genesi (uboot, Freescale)
Further down the list is the Toshiba AC100, which has semi-working uboot support, but uboot has no keyboard support for nvec attached keyboards, and it is Tegra2 based. The current way of booting them involves packaging up the kernel and initrd into a bootable partition image.
The only other platforms I can think of that somebody might want to run Fedora on are Compulab's ATX ARM board (Marvell based), and their TrimSlice micro desktop machine based on the Tegra2. Haven't used either of them yet, so don't know where they stand on uboot.
Depending on how many popular platforms I've missed, this may not be an unreasonable number to have custom kernels for.
Gordan
On Mon, 2011-02-28 at 12:17 +0000, Gordan Bobic wrote:
Dan Horák wrote: Standard kernels and bootloaders are something that will need to be looked at sooner or later, though. It might be an idea to start looking at what standard supported options might include. The most popular ones I can think of are (in no particular order):
SheevaPlugs (uboot, kirkwood) BeagleBoard/PandaBoard (uboot, OMAP) Genesi (uboot, Freescale)
We'll also want:
+OLPC XO 1.75 (openfirmware, Marvell Amanda 610)
-- Chris
On 28 February 2011 13:11, Chris Tyler chris@tylers.info wrote:
On Mon, 2011-02-28 at 12:17 +0000, Gordan Bobic wrote:
Dan Horák wrote: SheevaPlugs (uboot, kirkwood) BeagleBoard/PandaBoard (uboot, OMAP) Genesi (uboot, Freescale)
We'll also want:
+OLPC XO 1.75 (openfirmware, Marvell Amanda 610)
It might be an idea to have a per-board (or board-family) maintainer / point of contact. Then, provided the mainline kernel support is OK for those boards, could koji just build a set of kernel RPMs given a kernel config file? (Or am I being naive?)
I know my board (IGEPv2) has its own git repo, but I think (read: sincerely hope) the differences between that and mainline are becoming smaller.
Matthew
On Mon, Feb 28, 2011 at 10:55 AM, Matthew Wilson mj.wilson.uk@googlemail.com wrote:
On 28 February 2011 13:11, Chris Tyler chris@tylers.info wrote:
On Mon, 2011-02-28 at 12:17 +0000, Gordan Bobic wrote:
Dan Horák wrote: SheevaPlugs (uboot, kirkwood) BeagleBoard/PandaBoard (uboot, OMAP) Genesi (uboot, Freescale)
We'll also want:
+OLPC XO 1.75 (openfirmware, Marvell Amanda 610)
It might be an idea to have a per-board (or board-family) maintainer / point of contact. Then, provided the mainline kernel support is OK for those boards, could koji just build a set of kernel RPMs given a kernel config file? (Or am I being naive?)
I know my board (IGEPv2) has its own git repo, but I think (read: sincerely hope) the differences between that and mainline are becoming smaller.
Matthew
For a quick omap kernel for you guys, it's pretty safe to just build and package mainline kernel based off "omap2plus_config" defconfig..
Regards,
On 1/03/2011 12:11 AM, Chris Tyler wrote:
On Mon, 2011-02-28 at 12:17 +0000, Gordan Bobic wrote:
Dan Horák wrote: Standard kernels and bootloaders are something that will need to be looked at sooner or later, though. It might be an idea to start looking at what standard supported options might include. The most popular ones I can think of are (in no particular order):
SheevaPlugs (uboot, kirkwood) BeagleBoard/PandaBoard (uboot, OMAP) Genesi (uboot, Freescale)
We'll also want:
+OLPC XO 1.75 (openfirmware, Marvell Amanda 610)
gumstix overo (uboot, OMAP) Would be useful and there are quite a lot out there.
Apple tv ? ( uboot? , A4 )
qualcom arm chips - (uboot ,snapdragon)
Has anyone got access to any of the Nvidia dev boards (Tegra 2) ? http://developer.nvidia.com/tegra/tegra-devkit-features http://developer.download.nvidia.com/tegra/docs/tegra_250_hw_setup.pdf or http://www.linuxfordevices.com/c/a/News/MSC-Q7NT2-/
ST-Ericson Snowball board (uboot , ST-Ericsson Nova A9 ) dual A9 1GHz + mali 400 graphics http://www.calao-systems.com/articles.php?lng=en&pg=6186 http://www.calao-systems.com/articles.php?lng=en&pg=6186 http://www.igloocommunity.org/ http://www.linuxfordevices.com/c/a/News/Calao-Systems-Snowball/
i.MX53 Quick Start board - Freescales new one US$149 (uboot , i.MX53) http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB&... http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB&tid=vanimxquickstart http://www.linuxfordevices.com/c/a/News/Freescale-iMX537-and-iMX538-plus-Qui...
Also any plans for console and gui prebuilt images ? i.e along the lines of the ansgrtom-distribution console , palmtop and desktop images
Or just console then add the rest via yum ?
Alex
-- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology, Sydney. Before opening any attachments, please check them for viruses and defects.
Chris Tyler píše v Po 28. 02. 2011 v 08:11 -0500:
On Mon, 2011-02-28 at 12:17 +0000, Gordan Bobic wrote:
Dan Horák wrote: Standard kernels and bootloaders are something that will need to be looked at sooner or later, though. It might be an idea to start looking at what standard supported options might include. The most popular ones I can think of are (in no particular order):
SheevaPlugs (uboot, kirkwood) BeagleBoard/PandaBoard (uboot, OMAP) Genesi (uboot, Freescale)
We'll also want:
+OLPC XO 1.75 (openfirmware, Marvell Amanda 610)
summarized at https://fedoraproject.org/wiki/Architectures/ARM/Team_and_Developers#Archite...
Dan
On Tue, Mar 1, 2011 at 10:20 AM, Dan Horák dan@danny.cz wrote:
Chris Tyler píše v Po 28. 02. 2011 v 08:11 -0500:
On Mon, 2011-02-28 at 12:17 +0000, Gordan Bobic wrote:
Dan Horák wrote: Standard kernels and bootloaders are something that will need to be looked at sooner or later, though. It might be an idea to start looking at what standard supported options might include. The most popular ones I can think of are (in no particular order):
SheevaPlugs (uboot, kirkwood) BeagleBoard/PandaBoard (uboot, OMAP) Genesi (uboot, Freescale)
We'll also want:
+OLPC XO 1.75 (openfirmware, Marvell Amanda 610)
summarized at https://fedoraproject.org/wiki/Architectures/ARM/Team_and_Developers#Archite...
Cool, nice starting point. I have added myself for BeagleBoard interest.
I guess that the nicest way to create a kernel package, would be a similar solution to the kernel.i686 and kernel-PAE.i686 as it was in Fedora-12. They came from the same srpm. Alternatively it would be possible to have different srpms to provide the different boards, but I expect that this will cost more overhead in providing updates.
Any thoughts? Niels
-
Alex Gibson -
Chris Tyler -
Dan Horák -
Gordan Bobic -
Matthew Wilson -
Niels de Vos -
Robert Nelson