All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH arm: initial TI-Nspire support]
Date: Sat, 6 Apr 2013 13:51:00 +0200	[thread overview]
Message-ID: <201304061351.00889.arnd@arndb.de> (raw)
In-Reply-To: <8FB21B56-58BC-4530-8C7A-71A32856210D@gmail.com>

On Saturday 06 April 2013, Daniel Tang wrote:
> Hi,
> 
> First of all, thank you for your comments!
> 
> On 04/04/2013, at 10:12 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> 
> > For new platforms, we want to have only the absolute minimum amount of
> > code in arch/arm and move everything else into drivers. However, that
> > is only possible using device tree. It should not add any significant
> > complexity to your code, and you can easily bundle the device tree blob
> > with the kernel.
> 
> Given that most of your comments described some very fundamental changes
> (esp switching to DTB) to the structure of our port, we've decided we'll
> probably start from scratch and fix the issues you outlined as we
> reimplement our platform.
> 
> At the moment, we're working on getting a basic DTB-booting kernel working
> so our next patch will be starting from basics.

Ok, whichever way you prefer. If you have questions while working on this,
feel free to join #armlinux on irc.freenode.net, there are usually other
people working on the same things.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Tang <dt.tangr@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk,
	fabian@ritter-vogt.de, Lionel Debroux <lionel_debroux@yahoo.fr>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH arm: initial TI-Nspire support]
Date: Sat, 6 Apr 2013 13:51:00 +0200	[thread overview]
Message-ID: <201304061351.00889.arnd@arndb.de> (raw)
In-Reply-To: <8FB21B56-58BC-4530-8C7A-71A32856210D@gmail.com>

On Saturday 06 April 2013, Daniel Tang wrote:
> Hi,
> 
> First of all, thank you for your comments!
> 
> On 04/04/2013, at 10:12 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> 
> > For new platforms, we want to have only the absolute minimum amount of
> > code in arch/arm and move everything else into drivers. However, that
> > is only possible using device tree. It should not add any significant
> > complexity to your code, and you can easily bundle the device tree blob
> > with the kernel.
> 
> Given that most of your comments described some very fundamental changes
> (esp switching to DTB) to the structure of our port, we've decided we'll
> probably start from scratch and fix the issues you outlined as we
> reimplement our platform.
> 
> At the moment, we're working on getting a basic DTB-booting kernel working
> so our next patch will be starting from basics.

Ok, whichever way you prefer. If you have questions while working on this,
feel free to join #armlinux on irc.freenode.net, there are usually other
people working on the same things.

	Arnd

  reply	other threads:[~2013-04-06 11:51 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  9:01 [RFC PATCH arm: initial TI-Nspire support] Daniel Tang
2013-04-04  9:01 ` Daniel Tang
2013-04-04 11:12 ` Arnd Bergmann
2013-04-04 11:12   ` Arnd Bergmann
2013-04-06  0:26   ` Daniel Tang
2013-04-06  0:26     ` Daniel Tang
2013-04-06 11:51     ` Arnd Bergmann [this message]
2013-04-06 11:51       ` Arnd Bergmann
2013-04-06 12:00       ` Daniel Tang
2013-04-06 12:00         ` Daniel Tang
2013-04-06 13:24         ` Arnd Bergmann
2013-04-06 13:24           ` Arnd Bergmann
2013-04-07  0:06           ` Daniel Tang
2013-04-07  0:06             ` Daniel Tang
2013-04-07  3:56             ` Daniel Tang
2013-04-07  3:56               ` Daniel Tang
2013-04-07 21:23               ` Arnd Bergmann
2013-04-07 21:23                 ` Arnd Bergmann
2013-04-08 11:33                 ` Daniel Tang
2013-04-08 11:33                   ` Daniel Tang
2013-04-08 19:16                   ` Fabian Vogt
2013-04-08 19:16                     ` Fabian Vogt
2013-04-08 19:38                     ` Arnd Bergmann
2013-04-08 19:38                       ` Arnd Bergmann
2013-04-08 20:06                       ` Fabian Vogt
2013-04-08 20:06                         ` Fabian Vogt
2013-04-08 21:29                         ` Arnd Bergmann
2013-04-08 21:29                           ` Arnd Bergmann
2013-04-09  5:59                     ` Daniel Tang
2013-04-09  5:59                       ` Daniel Tang
2013-04-09 11:23                 ` Linus Walleij
2013-04-09 11:23                   ` Linus Walleij
2013-04-09 12:01                   ` Pawel Moll
2013-04-09 12:01                     ` Pawel Moll
2013-04-09 12:05                     ` Linus Walleij
2013-04-09 12:05                       ` Linus Walleij
2013-04-09 13:51                     ` Russell King - ARM Linux
2013-04-09 13:51                       ` Russell King - ARM Linux
2013-04-07 14:32             ` Arnd Bergmann
2013-04-07 14:32               ` Arnd Bergmann
2013-04-09 11:14 ` Linus Walleij
2013-04-09 11:14   ` Linus Walleij
2013-04-09 11:39   ` Daniel Tang
2013-04-09 11:39     ` Daniel Tang
2013-04-09 11:58     ` Linus Walleij
2013-04-09 11:58       ` Linus Walleij

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=201304061351.00889.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.