From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: PATCH, RFC: Generic DMA framework
Date: Sat, 25 Aug 2007 01:33:38 +0200 [thread overview]
Message-ID: <46CF6AD2.7040905@bellard.org> (raw)
In-Reply-To: <200708242118.54118.paul@codesourcery.com>
Paul Brook wrote:
> On Friday 24 August 2007, Blue Swirl wrote:
>> I have now converted the ISA DMA devices (SB16, FDC), most PCI devices
>> and targets.
>>
>> gdma.diff: Generic DMA
>> pc_ppc_dma_to_gdma.diff: Convert x86 and PPC to GDMA
>> pc_sb16_to_gdma.diff: Convert SB16 to GDMA
>> pc_fdc_to_gdma.diff: FDC
>> pc_dma_cleanup.diff: Remove unused functions
>> sparc_gdma.diff: Convert Sparc32 to GDMA
>> sparc32_dma_esp_le_to_gdma.diff: Convert ESP and Lance
>> sun4c.diff: Preliminary Sun4c (Sparcstation-1) support
>> pci_gdma.diff: Convert PCI devices and targets
>>
>> Any comments? The patches are a bit intrusive and I can't test the
>> targets except that they compile.
>
> Shouldn't the PCI DMA object be a property of the PCI bus?
> ie. we don't want/need to pass it round as a separate parameter. It can be
> inferred form the device/bus.
I agree. Moreover the DMA is bus specific so I don't see a need to add a
generic DMA layer.
Regards,
Fabrice.
next prev parent reply other threads:[~2007-08-24 23:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 19:48 [Qemu-devel] PATCH, RFC: Generic DMA framework Blue Swirl
2007-08-16 18:18 ` [Qemu-devel] " Blue Swirl
2007-08-16 19:58 ` malc
2007-08-19 17:46 ` Blue Swirl
2007-08-24 19:40 ` Blue Swirl
2007-08-24 20:18 ` Paul Brook
2007-08-24 23:33 ` Fabrice Bellard [this message]
2007-08-25 0:29 ` Paul Brook
2007-08-26 11:30 ` Fabrice Bellard
2007-08-26 17:54 ` Blue Swirl
2007-08-28 19:03 ` Blue Swirl
2007-08-28 19:43 ` Paul Brook
2007-08-29 17:00 ` Blue Swirl
2007-08-29 20:39 ` Paul Brook
2007-08-29 21:18 ` Paul Brook
2007-09-08 14:07 ` Blue Swirl
2007-09-08 14:31 ` Paul Brook
2007-09-08 14:53 ` Blue Swirl
2007-09-08 16:03 ` Paul Brook
2007-09-15 16:16 ` Blue Swirl
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=46CF6AD2.7040905@bellard.org \
--to=fabrice@bellard.org \
--cc=qemu-devel@nongnu.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).