Linux Driver Porting Advice

[John J. Karcher]

On 4/8/21 8:15 AM, Alexander Boettcher wrote:
> Hello,
> 
> On 08.04.21 05:59, John J. Karcher wrote:

[snip]

>> Using this approach, I have been able to reduce the number of build 
>> errors.  It looks like there are only a few left (although this could 
>> easily be a mirage).  But I'm stumbling on conflicting headers, which 
>> has led me to an interesting discovery - the 
>> "build/x86_64/var/libcache/usb_hid_include/include/include/include/linux/" 
>> directory, which is filled with symlinks to 
>> "repos/dde_linux/src/drivers/usb_hid/lx_emul.h".
>>
>> Second question: Where is this controlled?  I assume that if I pull in 
>> the real "device.h", for example, I should be able to remove 
>> "device.h" from a list somewhere that generates these symlinks.  Is 
>> that correct?
> 
> The symbolic links are generated by the mk file of the ported driver, 
> e.g. read 
> https://genode.org/documentation/developer-resources/porting_device_drivers#Further_preparations 
> for the basic idea.
> In your case, it is done in repos/dde_linux/lib/mk/usb_hid_include.mk.

I forgot about that article - it's exactly what I was looking for.

  Thanks!

   John J. Karcher
   devuser at alternateapproach.com