Date: Fri, 24 Mar 2017 17:59:18 -0700 From: Conrad Meyer <cem@freebsd.org> To: Christopher Bowman <crb@chrisbowman.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: large PCIe BARs Message-ID: <CAG6CVpW0MC%2Bs=j8hW5MP=i_s-c68=V-J-_icorB%2Bin-a8x4n5g@mail.gmail.com> In-Reply-To: <21FF81F3-D290-4682-AB88-5769C52499C3@chrisbowman.com> References: <21FF81F3-D290-4682-AB88-5769C52499C3@chrisbowman.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Christopher, Yeah, FreeBSD can easily map BARs that large. I've personally mapped a 512GB BAR, although I don't recommend it. We regularly use 32GB BARs. This might just be a driver bug. Best, Conrad On Fri, Mar 24, 2017 at 5:38 PM, Christopher Bowman <crb@chrisbowman.com> wrote: > I have an FPGA PCIe device and driver I designing. I think my driver is trying to map the PCIe address space for one of the BARs and it’s failing. My guess is that it’s failing due to the size. The board has 2G of onboard memory that I’d like to present as one large BAR. Does FreeBSD (11.0 release) allow for mapping PCIe resources that larger? If not is there a limit? If so any one have any comments? > Thanks, > Christopher > > sp6050: probing for SP605 > sp6050: <Xilinx SP605 board> at device 0.0 on pci3 > sp6050: attach of SP605 > sp6050: 0x40000000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). > sp6050: Could not map memory > device_attach: sp6050 attach returned 6 > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpW0MC%2Bs=j8hW5MP=i_s-c68=V-J-_icorB%2Bin-a8x4n5g>