MobileRead Forums - View Single Post

davidfor · 05-14-2015, 08:11 PM

I'm not sure what there is to decode. The vendor id is there and it is the same for all Kobo ereaders. The product ids are there for two of the models. There are a lot more models. They are defined in a subclass that is in the same source file that jackie_w referred to.

And as I have seen your other posts for similar details, all of the ereaders that calibre supports are defined in a similar way. Under the devices directory, there is a directory for each brand. Within that, is usually a driver.py. This can have or more classes for the models from the brand. Each class will have the list of vendor ids and product ids that he driver/class support.

05-14-2015, 08:11 PM	#4
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	I'm not sure what there is to decode. The vendor id is there and it is the same for all Kobo ereaders. The product ids are there for two of the models. There are a lot more models. They are defined in a subclass that is in the same source file that jackie_w referred to. And as I have seen your other posts for similar details, all of the ereaders that calibre supports are defined in a similar way. Under the devices directory, there is a directory for each brand. Within that, is usually a driver.py. This can have or more classes for the models from the brand. Each class will have the list of vendor ids and product ids that he driver/class support.