Control: tags 839595 pending
Pushed a commit to git:
https://anonscm.debian.org/git/d-i/flash-kernel.git/commit/?id=175f11c79927fbc9527f5cce1bdfd2ad60d3ed50
Should be included in the next upload.
live well,
vagrant
signature.asc
Description: PGP signature
Hi Vagrant, thanks for the reply.
On Sun, 23 Jul 2017 12:56:35 -0400 Vagrant Cascadian
wrote:
> On a related note, nobody has requested the clearfog target be enabled
> in the u-boot packages in Debian:
>
> https://wiki.debian.org/U-boot/
>
> If someone can offer to regularly test that, I'd be ha
On 2017-07-23, Josua Mayer wrote:
> Can anyone state the status here? If there is somethign missing, I'd be
> perfectly willing to conduct some tests on my board if necessary.
It looks like clearfog supports distro_bootcmd in mainline u-boot
2017.07 shipped in buster, including CONFIG_SUPPORT_RAW
* Christoph Egger [2016-12-27 17:55]:
> Christoph Egger writes:
> > I haven't updated u-boot yet, though it's still on my todo
>
> Seems to have worked. I have now u-boot 2016-11 SPL and "normal"
> u-boot and everything works so far \o/
Karsten, I think this one is waiting for you. Can you tak
Hi!
Christoph Egger writes:
> I haven't updated u-boot yet, though it's still on my todo
Seems to have worked. I have now u-boot 2016-11 SPL and "normal"
u-boot and everything works so far \o/
Christoph
signature.asc
Description: PGP signature
Hi all!
Christoph Egger writes:
> I'll try to get the results today/tomorrow night .. if I don't reply
> it'll be mid-january unfortunately
I added the snippet to /etc/flash-kernel/db now. I had to do the
following further steps (but I guess that's expected):
- put the adapted dtb at the kerne
Hi!
Martin Michlmayr writes:
> I was just looking at this bug report and it seems Karsten was never
> copied on Christoph's last email (see below).
Sorry for that. And I just didn't want to nag if people are busy.
Karsten Merker writes:
> that looks good. With this environment, using the "gene
I was just looking at this bug report and it seems Karsten was never
copied on Christoph's last email (see below).
* Christoph Egger [2016-10-24 15:22]:
> Hi!
>
> This seems to be the "new" default environment:
>
> => printenv
> arch=arm
> baudrate=115200
> board=clearfog
> board_name=clearfog
Hi!
This seems to be the "new" default environment:
=> printenv
arch=arm
baudrate=115200
board=clearfog
board_name=clearfog
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr}
${prefix}${script}; source ${scriptaddr}
boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpar
Hi!
Karsten Merker writes:
> The attached patch enables CONFIG_DISTRO_DEFAULTS and includes
> the necessary headers to define the common environment (only
> build-tested due to lack of appropriate hardware). One thing
> that is still missing in the patch is the definition of various
> default lo
Hi!
Karsten Merker writes:
> ext4load mmc 0:2 0x10 armada-388-clearfog.dtb ; ext4load mmc 0:2
> 0x80 vmlinuz-4.7.0-1-armmp ; ext4load mmc 0:2 0x180
> initrd.img-4.7.0-1-armmp ; bootz 0x80 0x180:${filesize}
> 0x10
=> ext4load mmc 0:2 0x10 armada-388-clearfog.dtb ; ext4
Hi!
Karsten Merker writes:
> Well, that is a _very_ minimalistic default environment ;-).
> So there isn't any boot command handling at all in the default
> environment of mainline u-boot for this system, which poses a
> problem for supporting this setup in flash-kernel.
I supposed this is CONFI
Hi!
Karsten Merker writes:
> is this the environment from mainline u-boot or the environment
> from the original Marvell u-boot? I ask because there are a few
> things that look a bit uncommon to me:
This is a mainline 2016.9 u-boot (clearfog_defconfig)
> - The bootcmd loads the kernel as a zI
Package: flash-kernel
Version: 3.69
Severity: wishlist
Hi!
Please consider adding clearfog support. The system works fine with
mainline u-boot + kernel. Hopefully I have added all necessary
information below:
| Machine: SolidRun Clearfog A1
| Kernel-Flavors: armmp armmp-lpae
| DTB-Id: armada-388
14 matches
Mail list logo