From: Markus Niebel <list-09_u-boot@tqsc.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch v2 0/7] Add support for TQMa6 modules
Date: Tue, 17 Jun 2014 19:40:53 +0200 [thread overview]
Message-ID: <53A07DA5.10502@tqsc.de> (raw)
In-Reply-To: <53A064FC.8030905@denx.de>
Am 17.06.2014 17:55, wrote Stefano Babic:
> Hi Markus,
>
> On 16/06/2014 18:51, Markus Niebel wrote:
>> From: Markus Niebel <Markus.Niebel@tq-group.com>
>>
>> This series add support for the TQMa6 boards from TQ Systems.
>> The first Patch adds basic support for the modiules and the
>> starterkit baseboard while the other patches add additional features
>>
>> Markus Niebel (7):
>> Add TQ Systems TQMa6 board support
>> TQMa6: mba6: add RGMII enet
>> TQMa6: add SPI support
>> TQMa6: add SPI NOR boot support
>> TQMa6: MBa6: add usb support
>> TQMa6: add I2C support
>> TQMa6: add pmic support
>>
>> board/tqc/tqma6/Makefile | 9 +
>> board/tqc/tqma6/README | 35 ++++
>> board/tqc/tqma6/clocks.cfg | 24 +++
>> board/tqc/tqma6/tqma6.c | 258 +++++++++++++++++++++++
>> board/tqc/tqma6/tqma6_bb.h | 30 +++
>> board/tqc/tqma6/tqma6_mba6.c | 358 +++++++++++++++++++++++++++++++
>> board/tqc/tqma6/tqma6q.cfg | 125 +++++++++++
>> board/tqc/tqma6/tqma6s.cfg | 125 +++++++++++
>> boards.cfg | 4 +
>> include/configs/tqma6.h | 477 ++++++++++++++++++++++++++++++++++++++++++
>
> I understand that your patchset follow your internal development.
> However, it is very uncommon that patches introducing new files are
> followed by patches changing the same files again.
>
> I think you should squash your patches. This makes easy to review them.
>
I thought to have at first a simple and restricted config / board support would be easier
to read, but no problem - will squash it.
> Do you take a look at the last patches to have a single image running on
> different variations of i.MX6 ? Dual and Quad are supported. Some work
> for the Solo is required.
>
> Is it not an attractive alternative for you ? Instead of having several
> entries in boards.cfg for each variation of your board, you could have
> maybe only one or a couple.
Sure it is - main difference will be boot devices. The env on different boot media
in one image is AFAIK not possible - so at the moment four configs are needed:
SP vs MMC and i.MX6Q/D vs i.MX6S (But this is slightly OT)
>
> Best regards,
> Stefano Babic
>
Best regards,
Markus Niebel
next prev parent reply other threads:[~2014-06-17 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 16:51 [U-Boot] [Patch v2 0/7] Add support for TQMa6 modules Markus Niebel
2014-06-16 16:51 ` [U-Boot] [Patch v2 1/7] Add TQ Systems TQMa6 board support Markus Niebel
2014-06-16 16:51 ` [U-Boot] [Patch v2 2/7] TQMa6: mba6: add RGMII enet Markus Niebel
2014-06-16 16:51 ` [U-Boot] [Patch v2 3/7] TQMa6: add SPI support Markus Niebel
2014-06-16 16:51 ` [U-Boot] [Patch v2 4/7] TQMa6: add SPI NOR boot support Markus Niebel
2014-06-16 16:51 ` [U-Boot] [Patch v2 5/7] TQMa6: MBa6: add usb support Markus Niebel
2014-06-16 16:51 ` [U-Boot] [Patch v2 6/7] TQMa6: add I2C support Markus Niebel
2014-06-16 16:51 ` [U-Boot] [Patch v2 7/7] TQMa6: add pmic support Markus Niebel
2014-06-17 15:55 ` [U-Boot] [Patch v2 0/7] Add support for TQMa6 modules Stefano Babic
2014-06-17 17:40 ` Markus Niebel [this message]
2014-06-17 17:58 ` Stefano Babic
2014-06-23 9:52 ` Markus Niebel
2014-06-23 10:07 ` Stefano Babic
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=53A07DA5.10502@tqsc.de \
--to=list-09_u-boot@tqsc.de \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox