Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 [2]

Author Topic: How do I blacklist a specific USB device at boot ?  (Read 6642 times)

Blackeagle

  • Reg Member
  • ***
  • Posts: 257
Re: How do I blacklist a specific USB device at boot ?
« Reply #15 on: March 18, 2014, 01:45:34 PM »

Hi mike  :thumbs:

I was going to look into it further (the blacklisting), but I ended up modding the kernel directly to not try and obtain a report from the display, and then building it from scratch.

This worked and now it appears, at least at the moment, that my driver works with LCDd. At the moment it's running on the target machine with XBMC and scrolling the time and date across the display.  Navigating to area's of XBMC are reflected on the display, as is the name of the TV station etc.

Much further testing is required to ensure that the driver is stable, with no memory leaks etc but so far so good !!  I might add that had I still been running an OS from Billy G, I wouldn't have even attempted to write a device driver, let alone actually managed it !!

B*eagle is feeling rather proud right now  :-[ :blush:
Logged
ASCII stupid question, get a stupid ANSI -- TalkTalk Broadband since 2006

Blackeagle

  • Reg Member
  • ***
  • Posts: 257
Re: How do I blacklist a specific USB device at boot ?
« Reply #16 on: March 23, 2014, 07:21:01 PM »

Further development is ongoing !!

I had hoped that as the LCDd server implements icons, that it would be possible to drive the custom icons on the display using it's standard icon output, but sadly this doesn't seem to be the case.  :no:

All I ever get returned from the XBMC client is a 'filled block' icon which is obviously no use. I have, as a 'proof of concept' enabled some checking of the strings scrolling across the display to light such icons as 'music', 'tv', 'photos' etc but as this is not in the spirit of LCDproc, I would hesitate to continue down this route and I did it purely to ensure I was driving the display correctly.

Having looked at drivers for LCD's that have custom icons (imon/mdm166a) reveals that one can send raw data to LCDd, provided the client supports doing this.  This is how the custom icons are driven for those displays.  If the client doesn't implement the raw output, then those icons will not work, but the basic display will.

So, as my driver implements the basics, we now have to turn to the client (in this case an add-on for XBMC) to see what information is returned.  Looking at the code for the iMon driver, it appears that volume level and pretty much any icon I could want are supported for that display.

Unfortunately for me, it's all python, which means trying to get my head around another language  :'(  At this moment I think I would rather have it written in C !!!

Plans as of now are to fork the current development branch of the XBMC LCDproc add-on and try an implement icon support for my display.  As all their code is GPL'd there's no problem doing that, or indeed hosting my own version of their addon.

It is an old case, and I doubt that there are all that many out there anymore, otherwise if I can get it working, I'd submit both the XBMC code and the LCDproc driver to the relevant places for inclusion in their software.  I am however, very pleased to see my display working after several years of being blank and although it's limited in what it can do, I have no intentions of changing cases anytime soon.
Logged
ASCII stupid question, get a stupid ANSI -- TalkTalk Broadband since 2006
Pages: 1 [2]