On 2021-06-18 12:19, Neel Chauhan wrote:
I'm not sure. I'll just note that the Linux code appears to be trying
to map a set of pages belonging to a scatter-gather list. Taking the
physical address of the first page and assuming that all subsequent
pages are physically contiguous doesn't seem
Hi Mark,
On 2021-06-18 06:57, Mark Johnston wrote:
That seems surprising, since the vm_page_grab() call should return the
page at pidx if one exists.
I believe that's not the case. I did pringfs
Any hints on where the physical address is? Should we have an
FreeBSD-specific "pa" argument for
On Jun 18, 2021, at 7:05 AM, Thomas Laus wrote:
>
> On 6/10/21 11:13 AM, Bakul Shah wrote:
>> This is what I did:
>>
>> git clone https://github.com/freebsd/drm-kmod
>> ln -s $PWD/drm-kmod /usr/local/sys/modules
>>
>> Now it gets compiled every time you do make buildkernel.
>> If things break
On 6/10/21 11:13 AM, Bakul Shah wrote:
> This is what I did:
>
> git clone https://github.com/freebsd/drm-kmod
> ln -s $PWD/drm-kmod /usr/local/sys/modules
>
> Now it gets compiled every time you do make buildkernel.
> If things break you can do a git pull in the drm-kmod dir
> and rebuild.
>
On Wed, Jun 16, 2021 at 10:16:56PM -0700, Neel Chauhan wrote:
> Hi Mark,
>
> Thank you so much for your response!
>
> On 2021-06-16 14:05, Mark Johnston wrote:
> >
> > The function in question appears to implement a device page fault
> > handler. In FreeBSD, such handlers are responsible only
The sha256 et.al. programs have recently been extended to provide
GNU compatible features if invoked as sha256sum.
This does now lead to port build issues, since there are ports that
assume that the -c option is implemented and that treat an error exit
of sha256sum -c as an indication of
