Am 19.05.2014 09:47, schrieb Guillaume Gardet:
> Le 18/05/2014 21:38, Andreas Färber a écrit :
>> I have succeeded in booting our newly built kernel-default package from
>> Kernel:HEAD on the Raspberry Pi model B with Factory and 3.15-rc2+.
> 
> Sounds good. :)
> 
> What is supported/unsupported compared to kernel-raspberrypi? Video output, 
> video encoding/decoding acceleration, 3D acceleration, sound, etc?

I didn't really do a comparison. On my previous tries, the
upstream-based, Kiwi-generated initrd resulted in processes getting
OOM-killed. The process I outlined should be Kiwi-compatible layout-wise
and once 3.15 hits Factory should become even easier.

HDMI and serial console output, booting from SDHCI (with the driver
addition), USB keyboard, network are all working.

Haven't got X11 installed yet.

For 3D acceleration AIUI there's a reverse-engineering project here:
https://github.com/hermanhermitage/videocoreiv-qpu
just as there is a reverse-engineering project for bootcode.bin:
https://github.com/hermanhermitage/videocoreiv

> Do you have a GPT or MBR partitioning?
> Could you give us your SD card partition layout, please?

I built on top of an earlier Kiwi image:

$ sudo /usr/sbin/parted /dev/mmcblk0
GNU Parted 3.1
Using /dev/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: SD SU16G (sd/mmc)
Disk /dev/mmcblk0: 15,9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  34,6MB  33,6MB  primary  fat16        type=06
 2      35,7MB  245MB   210MB   primary  ext3         type=07
 3      246MB   15,9GB  15,7GB  primary  ext4         type=83

Forgot two things:
1) Obviously I set /boot as the mount point for /dev/mmcblk0p2 in yast.
2) I now linked dtb-source into RaspberryPi:upstream so that we get a
dtb-bcm2835 package matching Kernel:HEAD. Happened to work for me as I
was on a previous bcm2835_defconfig 3.15 RC.

Would be really nice if we could get dtb-source linked into Kernel:HEAD
to avoid such Contrib trickery!

Another thing to be solved is that the firmware blobs install to /boot
when /boot is the ext3 partition. We need to decide on mount points,
have them set up in fstab and then adapt the install paths to be able to
update the binaries from a running system.

Cheers,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to