Re: makesyscalls

2020-06-12 Thread Reinoud Zandijk
On Wed, Jun 10, 2020 at 08:58:57AM +, David Holland wrote: > On Wed, Jun 10, 2020 at 01:25:03AM -0400, Thor Lancelot Simon wrote: > > Could you translate your prototype into a > > different language, one that's less basically hostile to our build system > > and its goals and benefits? > >

Re: pci_mapreg_map and BAR from `Bus space tutorial'

2020-06-12 Thread Rocky Hotas
Hello Radoslaw, On giu 11 1:02, Radoslaw Kujawa wrote: > It seems that in 2018 cobalt port was switched to common MIPS bus space > implementation. As a part of this implementation, it started to be more > strict about verification of addresses used by device during bus_space_map. [...] >

Re: pci_mapreg_map and BAR from `Bus space tutorial'

2020-06-12 Thread Mouse
>> [in your driver: extern int mapreg_debug; ... mapreg_debug = 1;] >> int mapreg_debug = 0; >> ... >> if (mapreg_debug) printf("...", ...); >> It's a horrible thing to do for "permanent" (production) code, but I >> see nothing at all wrong with it for experimental debugging. > Thank

Re: pci_mapreg_map and BAR from `Bus space tutorial'

2020-06-12 Thread Rocky Hotas
On giu 10 7:05, Mouse wrote: > You can't. If you have read-only access to the BAR - which is what > pcictl gives you - then all you can get is the base address. You need > read/write access to get the range as well. (In case you haven't yet > seen the trick: you read the value and save it,