* RE: [PATCH] Avoid PC(?) specific cascade dma reservation inkernel /dma.c
@ 2003-03-09 13:49 Mikael Starvik
2003-03-09 20:32 ` Alan Cox
0 siblings, 1 reply; 3+ messages in thread
From: Mikael Starvik @ 2003-03-09 13:49 UTC (permalink / raw)
To: 'Alan Cox', Johan Adolfsson
Cc: 'Marcelo Tosatti', 'Linus Torvalds',
'Linux Kernel Mailing List'
>I don't know of any PC cards that can support ISA DMA channel 4 so I
>guess simply because of that it hasn't happened. Do you actually
>know of any DMA 4 capable ISA devices or is it used for onboard
>ISA devices ?
In this case it is used in a non ISA capable system where DMA channel
numbers doesn't relate to ISA numbers in any way.
/Mikael
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: [PATCH] Avoid PC(?) specific cascade dma reservation inkernel /dma.c
2003-03-09 13:49 [PATCH] Avoid PC(?) specific cascade dma reservation inkernel /dma.c Mikael Starvik
@ 2003-03-09 20:32 ` Alan Cox
0 siblings, 0 replies; 3+ messages in thread
From: Alan Cox @ 2003-03-09 20:32 UTC (permalink / raw)
To: Mikael Starvik
Cc: Johan Adolfsson, 'Marcelo Tosatti',
'Linus Torvalds', 'Linux Kernel Mailing List'
On Sun, 2003-03-09 at 13:49, Mikael Starvik wrote:
> >I don't know of any PC cards that can support ISA DMA channel 4 so I
> >guess simply because of that it hasn't happened. Do you actually
> >know of any DMA 4 capable ISA devices or is it used for onboard
> >ISA devices ?
>
> In this case it is used in a non ISA capable system where DMA channel
> numbers doesn't relate to ISA numbers in any way.
So what happens if someone plugs a PCI/ISA bridge into an axis system.
Surely you should be reporting no ISA DMA and having a set of similar
axis specific DMA handlers - or does it really look so close to ISA think ?
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: [PATCH] Avoid PC(?) specific cascade dma reservation inkernel /dma.c
@ 2003-03-10 6:25 Mikael Starvik
0 siblings, 0 replies; 3+ messages in thread
From: Mikael Starvik @ 2003-03-10 6:25 UTC (permalink / raw)
To: 'Alan Cox', 'Mikael Starvik'
Cc: Johan Adolfsson, 'Marcelo Tosatti',
'Linus Torvalds', 'Linux Kernel Mailing List'
For CRIS the DMA channel numbers supplied refers to internal DMA
channels between the CPU and other units in the chip. The numbers
never refers to external units such as PCI devices or ISA devices.
If anybody would connect ISA or PCI the devices would all share
the same internal DMA. This may not be the intended usage of
kernel/dma.c and we could provide our own code to do the same
thing.
If kernel/dma.c should be as generic as it looks then the
reservation of DMA 4 as "cascade" should probably be done by
some other module (or by arch specific code).
/Mikael
-----Original Message-----
From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
Sent: Sunday, March 09, 2003 9:33 PM
To: Mikael Starvik
Cc: Johan Adolfsson; 'Marcelo Tosatti'; 'Linus Torvalds'; 'Linux Kernel
Mailing List'
Subject: RE: [PATCH] Avoid PC(?) specific cascade dma reservation
inkernel/dma.c
On Sun, 2003-03-09 at 13:49, Mikael Starvik wrote:
> >I don't know of any PC cards that can support ISA DMA channel 4 so I
> >guess simply because of that it hasn't happened. Do you actually
> >know of any DMA 4 capable ISA devices or is it used for onboard
> >ISA devices ?
>
> In this case it is used in a non ISA capable system where DMA channel
> numbers doesn't relate to ISA numbers in any way.
So what happens if someone plugs a PCI/ISA bridge into an axis system.
Surely you should be reporting no ISA DMA and having a set of similar
axis specific DMA handlers - or does it really look so close to ISA think ?
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-03-10 6:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-09 13:49 [PATCH] Avoid PC(?) specific cascade dma reservation inkernel /dma.c Mikael Starvik
2003-03-09 20:32 ` Alan Cox
2003-03-10 6:25 Mikael Starvik
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®