linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cbouatmailru@gmail.com (Anton Vorontsov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] Support for Cavium Networks CNS3xxx machines
Date: Wed, 14 Apr 2010 19:37:29 +0400	[thread overview]
Message-ID: <20100414153729.GA20979@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20100330190216.GA7611@oksana.dev.rtsoft.ru>

Hello,

On Tue, Mar 30, 2010 at 11:02:16PM +0400, Anton Vorontsov wrote:
> v3 is on the way...

Russell, does this look OK to you?

If so, I'll wait for the next mach-types update, and then will
ask you to pull the cns3xxx tree (or I can submit these patches
via the patch tracker if you prefer that).

Oh, and can you please take a look at these two as well:

[PATCH] ARM: Add support for PCI domains
 http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/012461.html
[PATCH] ARM: cns3xxx: Add support for PCI Express ports
 http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/012462.html

Thanks!

> Changes since v2:
> 
> - We noticed that timer2 (which was used as a clock source) causes
>   nanosleep system call to misbehave. Until debugged, the timer2
>   support is removed.
> 
>   It's fine since timer1 is still used as a clockevent, and provides
>   all needed timekeeping functionality. With these patches we want
>   a minimal (but rock solid) CNS3xxx support, all non-essential
>   features can wait.
> 
>   I.e. support for the second timer can be added as a separate
>   patch.
> 
> - Updated some PCIe register definitions to make PCIe integration
>   more smooth.
> 
> - Updated defconfig.
> 
> Changes since v1:
> 
> - Addressed Russell's comments;
> - CNS3420VB board support split into its own patch per Sergei's
>   comment;
> - This series no longer include AHCI and SDHCI patches. Because of
>   dependencies on other trees they aren't yet suitable for inclusion,
>   so no need to repost them again.

-- 
Anton Vorontsov
email: cbouatmailru at gmail.com
irc://irc.freenode.net/bd2

      parent reply	other threads:[~2010-04-14 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 19:02 [PATCH v3 0/3] Support for Cavium Networks CNS3xxx machines Anton Vorontsov
2010-03-30 19:02 ` [PATCH 1/3] ARM: cns3xxx: Add basic support for Cavium Networks CNS3xxx processors Anton Vorontsov
2010-04-14 15:40   ` Russell King - ARM Linux
2010-04-14 16:15     ` [PATCH v4 " Anton Vorontsov
2010-03-30 19:02 ` [PATCH 2/3] ARM: cns3xxx: Add CNS3420 Validation Board support Anton Vorontsov
2010-03-30 19:02 ` [PATCH 3/3] ARM: cns3xxx: Add defconfig for CNS3420 validation board Anton Vorontsov
2010-04-14 15:37 ` Anton Vorontsov [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=20100414153729.GA20979@oksana.dev.rtsoft.ru \
    --to=cbouatmailru@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).