From: Zhang Fuxin <fxzhang@ict.ac.cn>
To: Jun Sun <jsun@mvista.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Re: 8259 spurious interrupt (IRQ1,IRQ7,IRQ12..)
Date: Thu, 20 Sep 2001 9:52:0 +0800 [thread overview]
Message-ID: <200109200152.f8K1qne10137@oss.sgi.com> (raw)
hi,Jun Sun,
在 2001-09-19 12:39:00 you wrote:
>
>> >It is typically much easier to modify PCI device BARS so that they do coincide
>> >with the same physical address. You can control that by using the correct
>> >starting address for PCI MEM space in pci_auto.c resource assignment.
>> It seems a good way to solve the ioremap problem and X problem.But virt_to_bus
>> & bus_to_virt problem remains?
>>
>
>What is the virt_to_bus() problem? Is the address beyond 512MB (phy addr)?
No,I mean problem caused different cpu & pci address space.from pci's view,
the main memory is at address 0x80000000-0x90000000 in p6032.But for cpu,
they are 0x0-0x10000000.So current virt_to_bus & bus_to_virt won't work.
>If PCI mem (BUS) address is identical to phy addr, you should not have problem
>unless the address is beyond 512MB.
yes:).When i solve the 8259,i will try to make them same.
>
>BTW, virt_to_bus()/bus_to_virt() are deprecicated. See
>Documentation/DMA-mapping.txt.
I think the "depreciated" is only for direct usage: they are used in
arch/mips/pci-dma.c to implement new interface pci_alloc_consistent.
And there are still many driver using them(grep tell me).Am i missing
something?
>
>Jun
Regards
Zhang Fuxin
fxzhang@ict.ac.cn
next reply other threads:[~2001-09-20 1:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 1:52 Zhang Fuxin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-20 8:45 Re: 8259 spurious interrupt (IRQ1,IRQ7,IRQ12..) Phil Thompson
2001-09-19 10:27 Phil Thompson
2001-09-19 16:41 ` Ralf Baechle
2001-09-19 8:37 Zhang Fuxin
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=200109200152.f8K1qne10137@oss.sgi.com \
--to=fxzhang@ict.ac.cn \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
/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