| To: | JinuM <jinum@esntechnologies.co.in> |
|---|---|
| Subject: | Re: PCI Conf Space in application mode |
| From: | Alan Cox <alan@lxorguk.ukuu.org.uk> |
| Date: | 27 May 2003 00:33:12 +0100 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <AF572D578398634881E52418B2892567122B4C@mail.esn.activedirectory> |
| Organization: | |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <AF572D578398634881E52418B2892567122B4C@mail.esn.activedirectory> |
| Sender: | linux-mips-bounce@linux-mips.org |
> On my x86 system i do that using iopl() call n then accessing PCI Conf space > through ADDRESS port(0xCF8) and DATA port(0xCFC). Here i have no problems > accessing the IO ports. This is wrong. If the kernel does a PCI config access between your two accesses you will break the system. See pcilib as used by lspci |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: profiling SMP/SB1250, Jamal Hadi |
|---|---|
| Next by Date: | Re: [PATCH] Embedded ramdisks, Ralf Baechle |
| Previous by Thread: | Re: PCI Conf Space in application mode, Maciej W. Rozycki |
| Next by Thread: | [PATCH] Fix thinko in mips/mips64 sys_sysmips, Ben Collins |
| Indexes: | [Date] [Thread] [Top] [All Lists] |