From: arno@natisbad•org (Arnaud Ebalard)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv1 0/3] arm: mvebu: add Synology DS213j and DS414 .dts files
Date: Sun, 16 Nov 2014 14:24:03 +0100 [thread overview]
Message-ID: <874mtzb7nw.fsf@natisbad.org> (raw)
In-Reply-To: <20141116022035.GE15870@lunn.ch> (Andrew Lunn's message of "Sun, 16 Nov 2014 03:20:35 +0100")
Hi,
Andrew Lunn <andrew@lunn•ch> writes:
>> Andrew, in this v1, the two .dts files are still separate w/o any common
>> .dtsi. I took a quick look it seems there are small differences between
>> the two which make me wonder if its worth the trouble:
>>
>> - DS414 fans are not handled by the SoC
>> - various pinctrl variations
>> - a tiny difference in SPI flash partitioning
>> - phy-mode for ethernet interfaces
>> - different comments associated w/ same nodes (e.g. uart1)
>> - etc
>
> O.K, lets wait for the moment. It could be that there is more in
> common between different 370 devices, and between different XP
> devices, but less in common across 370 and XP.
>
> We can refactor it later when a pattern starts to appear.
ok.
>> - Added a comment in the .dts file about the bootloader screwing the kernel
>> if the environment is saved.
>
> Is this well know in the forums? Do you think Synology knows about it?
> It would be nice if it was fixed. Maybe not for these products, but
> for the next generation.
I never went to synology forum to check if someone had broken her NAS
doing a saveenv under u-boot. But I doubt that: doing a 'synology saveenv'
search on google gives DS213j .dts submission (with the comment on the
issue) as 10th link.
If you have some contact to provide, I can report it.
Cheers,
a+
prev parent reply other threads:[~2014-11-16 13:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 0:04 [PATCHv1 0/3] arm: mvebu: add Synology DS213j and DS414 .dts files Arnaud Ebalard
2014-11-16 0:04 ` [PATCHv1 1/3] arm: mvebu: add uartX labels for Armada SoC serial nodes Arnaud Ebalard
2014-11-16 1:09 ` Andrew Lunn
2014-11-16 12:34 ` Arnaud Ebalard
2014-11-16 0:04 ` [PATCHv1 2/3] arm: mvebu: add .dts file for Synology DS213j Arnaud Ebalard
2014-11-16 2:00 ` Andrew Lunn
2014-11-16 2:31 ` Andrew Lunn
2014-11-16 13:14 ` Arnaud Ebalard
2014-11-16 23:23 ` Ben Peddell
2014-11-17 8:25 ` Arnaud Ebalard
2014-11-17 22:41 ` Ben Peddell
2014-11-17 23:23 ` Arnaud Ebalard
2014-11-16 0:04 ` [PATCHv1 3/3] arm: mvebu: add .dts file for Synology DS414 Arnaud Ebalard
2014-11-16 2:15 ` Andrew Lunn
2014-11-16 13:17 ` Arnaud Ebalard
2014-11-16 2:20 ` [PATCHv1 0/3] arm: mvebu: add Synology DS213j and DS414 .dts files Andrew Lunn
2014-11-16 13:24 ` Arnaud Ebalard [this message]
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=874mtzb7nw.fsf@natisbad.org \
--to=arno@natisbad$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox