Date: Tue, 31 Jul 2012 09:14:41 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Venkat Duvvuru <venkatduvvuru.ml@gmail.com> Cc: freebsd-net@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: PCI BAR mmap Message-ID: <CAJ-VmokHYE_jT8i4B-m1Mz3aG60FyWLa7jHgsdXUwWz3qsPsjw@mail.gmail.com> In-Reply-To: <CAGdae7aw0M_BNy2ozbPhznC7vuw-5%2BbxqJVx%2BJBnhzG4TnKsYg@mail.gmail.com> References: <CAGdae7a0xuKnFaeOTUykLcUKuCf17TTuYD_MuG4t7FKbHNoqAg@mail.gmail.com> <201207310951.12251.jhb@freebsd.org> <CAGdae7aw0M_BNy2ozbPhznC7vuw-5%2BbxqJVx%2BJBnhzG4TnKsYg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31 July 2012 08:22, Venkat Duvvuru <venkatduvvuru.ml@gmail.com> wrote: > Hi John, > Thanks for your response. > Is there an alternative to mmap the PCI BARs, I mean without implementing > an mmap method in the driver, something like a pci subsystem mmap in Linux. > Linux allows to mmap PCI BARs without any change in the device driver. I guess someone could implement a sysctl API to access PCI BAR registers, rather than mapping /dev/pci or however pciconf -r works. That way you'd implement it once and all devices would have their BAR registers show up in a userland-friendly way. 2c, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokHYE_jT8i4B-m1Mz3aG60FyWLa7jHgsdXUwWz3qsPsjw>