On Wed, 2014-06-25 at 22:31 +0100, Stuart Winter wrote:
>
> > Did you try the appending method and have it work?
> >
> > Do e.g. the kernels currently in testing and/or experimental work for
> > you?
>
> Yes after appending the Sheevaplug DTB, I got this kernel to boot.
Great!
> 3.14-0.bpo.1-k
> Did you try the appending method and have it work?
>
> Do e.g. the kernels currently in testing and/or experimental work for
> you?
Yes after appending the Sheevaplug DTB, I got this kernel to boot.
3.14-0.bpo.1-kirkwood #1 Debian 3.14.7-1~bpo70+1 (2014-06-21)
> Other than that I think we a
On 24/06/2014 14:51, Ian Campbell wrote:
> On Tue, 2014-06-24 at 14:21 +0200, drEagle wrote:
>>> What about the uboots fdt commands [1] ?
>
> AFAIK that's mostly about modifying an in memory FDT, but it doesn't
> actual deal with passing it to the kernel, which is done by passing the
> address as
On Tue, 2014-06-24 at 16:19 +0100, Stuart Winter wrote:
> > > the FTD blob when it's been loaded itself.
> >
> > Not sure what you mean here. u-boot needs to be told to pass an fdt
> > (which must already be in RAM) by passing the address as the third
> > argument to bootm or bootz. If you don't ha
> > the FTD blob when it's been loaded itself.
>
> Not sure what you mean here. u-boot needs to be told to pass an fdt
> (which must already be in RAM) by passing the address as the third
> argument to bootm or bootz. If you don't have an initrd (the second
> argument) then use "-".
The DTB was l
On Tue, 2014-06-24 at 11:40 +0100, Stuart Winter wrote:
> However, I still don't know why U-Boot doesn't seem to be supplying
> the FTD blob when it's been loaded itself.
Not sure what you mean here. u-boot needs to be told to pass an fdt
(which must already be in RAM) by passing the address as t
On Tue, 2014-06-24 at 14:21 +0200, drEagle wrote:
> Sorry,
>
> Forgot the ML...
>
> On 24/06/2014 13:45, drEagle wrote:
> > Hi,
> >
> > Never tried for now the fdt commands; zimage cat method works just fine on
> > kirkwood and armada.
> >
> > On 23/06/2014 11:36, Stuart Winter wrote:
> > ...
Sorry,
Forgot the ML...
On 24/06/2014 13:45, drEagle wrote:
> Hi,
>
> Never tried for now the fdt commands; zimage cat method works just fine on
> kirkwood and armada.
>
> On 23/06/2014 11:36, Stuart Winter wrote:
> ...
>> Does anybody have any idea why it doesn't work or how to make it work?
On 23/06/2014 10:36, Stuart Winter wrote:
Hello
I'm hoping someone can help point out the way to make U-Boot work with
Flattened Device Tree on the SheevaPlug.
Marvell>> setenv bootargs earlyprintk console=ttyS0,115200n8 kbd=uk
nic=auto:eth0:dhcp root=/dev/ram rw
Marvell>> bootm 0x0080
> > isn't the 'dtb' supposed to be appended to the zImage and then the
> > uImage created with mkimage?
Thanks -- it dawned on me that this was the case after I had sent the
mail, so
I assume it will boot once I add it to the zImage - I'll test it shortly.
However, I still don't know why U-Boot
Hi Stuart,
I'm sorry this is going to be a non-answer as I haven't tried device tree
boot on my sheevaplug. Just wanted to answer this - "I don't believe that
the sheevaplug is actually an eSATA version - it doesn't have an eSATA port
-- maybe there's just support on board."
IIRC the original sh
On Mon, 2014-06-23 at 19:31 +0100, Michael Howard wrote:
> On 23/06/2014 10:36, Stuart Winter wrote:
> > Hello
> >
>
> Hi,
> Can't help you with much and may be off mark with the following but,
>
> >
> > My kernel has the support for appended DTBs so I also tried appending the
> > FDT blob to the
On 23/06/2014 10:36, Stuart Winter wrote:
Hello
Hi,
Can't help you with much and may be off mark with the following but,
My kernel has the support for appended DTBs so I also tried appending the
FDT blob to the uImage - again for both eSATA and regular Sheevaplug:
cat dtbfile.dtb >> uIma
Hello
I'm hoping someone can help point out the way to make U-Boot work with
Flattened Device Tree on the SheevaPlug.
I have the same Linux 3.15.1 kernel binary running on the OpenRD client,
but the OpenRD client has support baked into the kernel (presumably
because the OpenRD client has no newer
14 matches
Mail list logo
