From: "Guan Xuetao" <guanxuetao@mprc.pku.edu.cn>
To: "'Jesse Barnes'" <jbarnes@virtuousgeek.org>
Cc: <sfr@canb.auug.org.au>, "'Arnd Bergmann'" <arnd@arndb.de>,
<gregkh@suse.de>, <dmitry.torokhov@gmail.com>, <dtor@mail.ru>,
<rubini@cvml.unipv.it>, <linux-arch@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-fbdev@vger.kernel.org>,
<linux-next@vger.kernel.org>
Subject: RE: Request for unicore32 architecture codes to merge into linux-next
Date: Sat, 22 Jan 2011 10:17:16 +0800 [thread overview]
Message-ID: <013801cbb9da$7f9bff10$7ed3fd30$@mprc.pku.edu.cn> (raw)
In-Reply-To: <20110120114216.4b23182a@jbarnes-desktop>
> -----Original Message-----
> From: Jesse Barnes [mailto:jbarnes@virtuousgeek.org]
> Sent: Friday, January 21, 2011 3:42 AM
> To: Guan Xuetao
> Cc: sfr@canb.auug.org.au; Arnd Bergmann; gregkh@suse.de; dmitry.torokhov@gmail.com; dtor@mail.ru; rubini@cvml.unipv.it; linux-
> arch@vger.kernel.org; linux-kernel@vger.kernel.org; linux-fbdev@vger.kernel.org; linux-next@vger.kernel.org
> Subject: Re: Request for unicore32 architecture codes to merge into linux-next
>
> On Sun, 16 Jan 2011 01:00:31 +0800
> "Guan Xuetao" <guanxuetao@mprc.pku.edu.cn> wrote:
>
> > Hi,
> >
> > I want to merge unicore32 repo into linux-next tree, the position is (unicore32 branch):
> > git://git.kernel.org/pub/scm/linux/kernel/git/epip/linux-2.6-unicore32.git
> >
> > Signed-off-by: Guan Xuetao <gxt@mprc.pku.edu.cn>
> > ---
>
> Took a quick look at the PCI parts, looks like you have a pretty big
> DMA restriction.
Yes, only 128MB low memory could be used as dma space for pci devices.
>
> You could provide your own dma map ops and make the allocator a bit
> smarter about where it gets memory (preferentially allocating from the
> DMA'able region, which you could hide). Or do you find that swiotlb
> does ok in general?
Swiotlb works well. For almost all functions are provided by IPs inside the SoC,
the dma function is used mainly through amba/axi bus, not pci bus.
>
> Other than that you had pretty tiny bits of enabling code, I assume
> they work on your platform (config space access & setup, etc.).
Yes.
>
> --
> Jesse Barnes, Intel Open Source Technology Center
Thanks Jesse
Guan Xuetao
prev parent reply other threads:[~2011-01-22 2:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 17:00 Guan Xuetao
2011-01-15 22:08 ` Dmitry Torokhov
2011-01-16 15:35 ` Guan Xuetao
2011-01-18 4:33 ` Paul Mundt
2011-01-18 9:07 ` Guan Xuetao
2011-01-18 9:10 ` Paul Mundt
2011-01-18 9:33 ` Guan Xuetao
2011-01-18 9:53 ` Paul Mundt
2011-01-18 18:33 ` Konrad Rzeszutek Wilk
2011-01-19 2:20 ` Guan Xuetao
2011-01-20 19:42 ` Jesse Barnes
2011-01-22 2:17 ` Guan Xuetao [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='013801cbb9da$7f9bff10$7ed3fd30$@mprc.pku.edu.cn' \
--to=guanxuetao@mprc.pku.edu.cn \
--cc=arnd@arndb.de \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@mail.ru \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rubini@cvml.unipv.it \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®