linux-kernel - Re: Accessing 64-bit BARs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b681c62b0710042057m6942eb72t498e4f59ebd8ae3a@mail.gmail.com>
Date:	Fri, 5 Oct 2007 09:27:25 +0530
From:	"yogeshwar sonawane" <yogyas@...il.com>
To:	"Roland Dreier" <rdreier@...co.com>
Cc:	"Rolf Eike Beer" <eike-kernel@...tec.de>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Accessing 64-bit BARs

hello,
Thanks rolf & roland.

pci_iomap() is not doing something extra. only it is some kind of
abstraction for IO-mapped OR memory mapped.
I know that my BARs are MMIO, so using ioremap() & readl()/writel()
combination should be fine.

But for the problem as explained in my first mail, any
help/suggestions will be helpful.

-Yogeshwar

On 10/4/07, Roland Dreier <rdreier@...co.com> wrote:
>  > You should use pci_iomap() to get an access pointer to the BAR. After this you
>  > can access the memory with ioread*() and iowrite*(). See "man pci_iomap(9)"
>  > if you build kernel manpages.
>
> That works fine, but ioremap() and readl()/writel() is also perfectly
> fine for regions that you know are always MMIO.
>
>  - R.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/