From: Alexander Aring <alex.aring@gmail.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC 2/2] dns325: initial support for D-Link DNS-325
Date: Mon, 23 Jun 2014 08:48:31 +0200 [thread overview]
Message-ID: <20140623064829.GA9990@omega> (raw)
In-Reply-To: <53A74FC0.7080206@gmail.com>
On Sun, Jun 22, 2014 at 11:50:56PM +0200, Sebastian Hesselbarth wrote:
> On 06/22/2014 10:34 PM, Alexander Aring wrote:
> > This patch add a basic support for the D-Link DNS-325.
> >
> > Currently only booting via uart with kwboot is supported. The barebox
> > kwboot utility doesn't work at the moment. Use kwboot utility from u-boot
> > instead.
>
> Why does kwboot does not work? There is an issue with early Kirkwood's
> BootROM and UART boot mode. Just try over and over again. I also recall
> modifying the timeouts may help.
>
Ok, I will dig into this issue next weekend.
> > Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> > ---
> [...]
> > diff --git a/arch/arm/boards/dlink-dns325/dlink-dns325.dox b/arch/arm/boards/dlink-dns325/dlink-dns325.dox
> > new file mode 100644
> > index 0000000..414b2e7
> > --- /dev/null
> > +++ b/arch/arm/boards/dlink-dns325/dlink-dns325.dox
> > @@ -0,0 +1,37 @@
> > +/** @page dlink-dns325 D-Link DNS-325 NAS
> > +
> > +The NAS has
> > +@li Kirkwood 88F6281-A1 SoC
> > +@li 256 MB SDRAM
> > +@li 128 MB NAND type SAMSUNG 946 K9F1G08U0B PCB0
> > +@li 2 SATA interfaces
> > +@li RS232 serial interface
> > +@li 1 USB interface
> > +@li 1 Gigabit Ethernet interface
> > +@li 1 Temp Sensor G751-2f
> > +@li 1 MCU Holtek HT48C06E for Power Managment
> > +@li LEDs & buttons
> > +
> > +The NAS doesn't support NAND right now.
> > +Only boot via uart with kwboot is supported.
>
> Is it the NAS that doesn't support NAND or is it missing driver support
> for barebox instead?
ehm yes, there is a missing driver in barebox. Thanks for pointing this
out.
Are there any suggestions to implement "8-bit NAND Flash Interface" for
the kirkwoods 88F6180/88F619x/88F6281?
This platform is "just for fun" currently, not very useful without mtd
support. :-)
The free kirkwoods sheets are well documented, maybe I could try this.
Or port some code from linux/u-boot.
But first I will fix the kwboot issue, of course.
>
> > +The kwboot utility of barebox doesn't work right now.
> > +Instead use the u-boot kwboot utility:
>
> See above, we should fix kwboot instead.
>
Ok.
Thanks.
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-06-23 6:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 20:34 [RFC 1/2] kirkwood: add support for booting via oftree probe Alexander Aring
2014-06-22 20:34 ` [RFC 2/2] dns325: initial support for D-Link DNS-325 Alexander Aring
2014-06-22 21:50 ` Sebastian Hesselbarth
2014-06-23 6:48 ` Alexander Aring [this message]
2014-06-26 4:27 ` Alexander Aring
2014-06-26 6:53 ` Sebastian Hesselbarth
2014-06-26 9:14 ` Alexander Aring
2014-06-24 11:54 ` Sebastian Hesselbarth
2014-06-25 6:57 ` Sascha Hauer
2014-06-22 21:45 ` [RFC 1/2] kirkwood: add support for booting via oftree probe Sebastian Hesselbarth
2014-06-23 6:51 ` Alexander Aring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140623064829.GA9990@omega \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.