[Bug 1578505] Re: Raspberry Pi 3 support
Ryan Finnie
ryan.finnie at canonical.com
Thu May 5 06:11:17 UTC 2016
** Patch added: "flash-kernel-3.0~rc.4ubuntu63.debdiff"
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1578505/+attachment/4656132/+files/flash-kernel-3.0~rc.4ubuntu63.debdiff
** Description changed:
- Debdiff to follow.
-
Note that this makes a few assumptions:
1) Will not work as-is; updated u-boot and linux-firmware-raspi2 will
also be required. I'm testing with u-boot HEAD and raspberrypi/firmware
HEAD. Details at https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3
2) For some reason, u-boot mkenvimage creates a uboot.env using the RPi2
config which u-boot just doesn't read, citing a CRC error. This occurs
even when using mkenvimage from HEAD. I'm still trying to determine if
it's a bug with u-boot, but boot.scr works fine. I've translated the
uboot.env to its equivalent boot.scr script and it works fine, so I
don't see why we can't just use boot.scr on the RPi3. (saveenv within
the u-boot shell writes a uboot.env which it can subsequently re-read,
interestingly.)
3) The all.db entry, minus the move to boot.scr, is based on the RPi2
entry above, right down to the "XXX".
** Description changed:
Note that this makes a few assumptions:
1) Will not work as-is; updated u-boot and linux-firmware-raspi2 will
also be required. I'm testing with u-boot HEAD and raspberrypi/firmware
HEAD. Details at https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3
2) For some reason, u-boot mkenvimage creates a uboot.env using the RPi2
- config which u-boot just doesn't read, citing a CRC error. This occurs
- even when using mkenvimage from HEAD. I'm still trying to determine if
- it's a bug with u-boot, but boot.scr works fine. I've translated the
- uboot.env to its equivalent boot.scr script and it works fine, so I
- don't see why we can't just use boot.scr on the RPi3. (saveenv within
- the u-boot shell writes a uboot.env which it can subsequently re-read,
- interestingly.)
+ config which u-boot HEAD just doesn't read, citing a CRC error. This
+ occurs even when using mkenvimage from HEAD. I'm still trying to
+ determine if it's a bug with u-boot, but boot.scr works fine. I've
+ translated the uboot.env to its equivalent boot.scr script and it works
+ fine, so I don't see why we can't just use boot.scr on the RPi3.
+ (saveenv within the u-boot shell writes a uboot.env which it can
+ subsequently re-read, interestingly.)
3) The all.db entry, minus the move to boot.scr, is based on the RPi2
entry above, right down to the "XXX".
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to flash-kernel in Ubuntu.
https://bugs.launchpad.net/bugs/1578505
Title:
Raspberry Pi 3 support
Status in flash-kernel package in Ubuntu:
New
Bug description:
Note that this makes a few assumptions:
1) Will not work as-is; updated u-boot and linux-firmware-raspi2 will
also be required. I'm testing with u-boot HEAD and
raspberrypi/firmware HEAD. Details at
https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3
2) For some reason, u-boot mkenvimage creates a uboot.env using the
RPi2 config which u-boot HEAD just doesn't read, citing a CRC error.
This occurs even when using mkenvimage from HEAD. I'm still trying to
determine if it's a bug with u-boot, but boot.scr works fine. I've
translated the uboot.env to its equivalent boot.scr script and it
works fine, so I don't see why we can't just use boot.scr on the RPi3.
(saveenv within the u-boot shell writes a uboot.env which it can
subsequently re-read, interestingly.)
3) The all.db entry, minus the move to boot.scr, is based on the RPi2
entry above, right down to the "XXX".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1578505/+subscriptions
More information about the foundations-bugs
mailing list