From: khc@pm.waw.pl (Krzysztof Halasa)
To: linux-arm-kernel@lists.infradead.org
Subject: ixp4xx support in newer kernels
Date: Thu, 19 Aug 2010 19:04:32 +0200 [thread overview]
Message-ID: <m3wrrmr0tb.fsf@intrepid.localdomain> (raw)
In-Reply-To: <AANLkTin-A2ubhzsn0DGD2vWn1RxougLV=4V-CS3VcNWe@mail.gmail.com> (y. bhanu's message of "Wed, 18 Aug 2010 00:48:34 -0700")
Hi,
y bhanu <kernelccrazy@gmail.com> writes:
> I am starting off on a new project with ixp4xx based chip.
> I already have it working in 2.6.19 kernel.
> How well are ixp432/ixp435 chips supported in new kernels.
> I would like to move it to 2.6.35 kernel.
>
> If I want to look at the latest patched for IXP4xx, is there good spot
> to look at ( gitweb or URL).
They should work fine, except possibly a problem with "coherent" memory
allocations, which is being worked on, and for which a usable patch is
available.
--
Krzysztof Halasa
next prev parent reply other threads:[~2010-08-19 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 7:48 ixp4xx support in newer kernels y bhanu
2010-08-19 17:04 ` Krzysztof Halasa [this message]
2010-08-22 15:52 ` Hendrik Sattler
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=m3wrrmr0tb.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--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