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 uImage -
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
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
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
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?
I would
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:
...
Does anybody
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
On Thu, 2014-06-19 at 07:58 +0100, Michael Howard wrote:
On 18/06/2014 19:41, Ian Campbell wrote:
On Wed, 2014-06-18 at 17:46 +0100, Michael Howard wrote:
Anybody tried a standard 'debian-installer' install recently on the
Dreamplug?
Not recently. I'm about to leave on a trip so I won't
On 24/06/2014 13:55, Ian Campbell wrote:
On Thu, 2014-06-19 at 07:58 +0100, Michael Howard wrote:
On 18/06/2014 19:41, Ian Campbell wrote:
On Wed, 2014-06-18 at 17:46 +0100, Michael Howard wrote:
Anybody tried a standard 'debian-installer' install recently on the
Dreamplug?
Not recently.
Ian Campbell ijc at hellion.org.uk writes:
TL;DR: Please run the attached kirkwood-qnap script on your ARM based
QNAP systems as ./kirkwood-qnap --info and report the results in this
thread along with the model/kind of your QNAP device (as precisely as
you can).
$ ./kirkwood-info.sh
.: 87:
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 loaded
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 have an
Hello,
since I have to reinstall my NAS on a new HDD, I thought it would be a good
idea to set up encryption this time. But I'm not sure how exactly I should
start on this.
I think the standard way to do this is using the dm-crypt facilities built
into the Debian installer. Now, will this work
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 the
On Tue, 2014-06-24 at 17:18 +0200, Lee Williams wrote:
Hello,
since I have to reinstall my NAS on a new HDD, I thought it would be a
good idea to set up encryption this time. But I'm not sure how exactly
I should start on this.
I think the standard way to do this is using the dm-crypt
On Wed, 2014-06-18 at 10:59 +0100, David Pottage wrote:
On 17/06/14 08:49, Ian Campbell wrote:
Hello,
TL;DR: Please run the attached kirkwood-qnap script on your ARM based
QNAP systems as ./kirkwood-qnap --info and report the results in this
thread along with the model/kind of your QNAP
On Tue, 2014-06-24 at 15:12 +, Phil Endecott wrote:
Ian Campbell ijc at hellion.org.uk writes:
TL;DR: Please run the attached kirkwood-qnap script on your ARM based
QNAP systems as ./kirkwood-qnap --info and report the results in this
thread along with the model/kind of your QNAP
On Tue, 2014-06-17 at 08:49 +0100, Ian Campbell wrote:
Hello,
TL;DR: Please run the attached kirkwood-qnap script on your ARM based
QNAP systems as ./kirkwood-qnap --info and report the results in this
thread along with the model/kind of your QNAP device (as precisely as
you can). The
On Tue, Jun 24, 2014 at 7:56 PM, Ian Campbell i...@hellion.org.uk wrote:
On Tue, 2014-06-24 at 17:18 +0200, Lee Williams wrote:
Lee, are you on the list or should we continue to cc?
Hello,
since I have to reinstall my NAS on a new HDD, I thought it would be a
good idea to set up
On 24/06/2014 18:01, Ian Campbell wrote:
On Tue, 2014-06-24 at 15:20 +0100, Michael Howard wrote:
As I was trying a fresh install I first used the current images (kernel
initrd) from wheezy. I then tried jessie and when that failed I tried
the last images from squeeze. All failed at the same
20 matches
Mail list logo
