Quote:
Originally Posted by tshering
I did not try to match systematically the PCB values with models, but my list for code names, model identification numbers (as used for determining the FW update file) and product ids is as follows:
trilogy 310 Kobo Touch 0x4163
trilogy 320 Kobo TouchC 0x4163
kraken 330 Kobo Glo 0x4173
pixie 340 Kobo Mini 0x4183
dragon 350 AuraHD 0x4193
phoenix 360 Aura 6" 0x4203
dahlia 370 AuraH2O 0x4213
alyssum 371 GloHD 0x4223
pika 372 Touch 2 0x4224
daylight 373 Aura One 0x4225
snow 374 Aura H2O 2 0x4227
star 375 Aura Edition 2 0x4226
Sure, I might be wrong.
|
That looks right to me. To throw more info on it, I have the following in the KoboTouch driver in calibre:
Code:
AURA_PRODUCT_ID = [0x4203]
AURA_EDITION2_PRODUCT_ID = [0x4226]
AURA_HD_PRODUCT_ID = [0x4193]
AURA_H2O_PRODUCT_ID = [0x4213]
AURA_H2O_EDITION2_PRODUCT_ID = [0x4227]
AURA_ONE_PRODUCT_ID = [0x4225]
GLO_PRODUCT_ID = [0x4173]
GLO_HD_PRODUCT_ID = [0x4223]
MINI_PRODUCT_ID = [0x4183]
TOUCH_PRODUCT_ID = [0x4163]
TOUCH2_PRODUCT_ID = [0x4224]
And the latest kobo_config.sh from the firmware I have is:
Code:
#!/bin/sh
#!/bin/sh
PCB=`ntx_hwconfig -s -p /dev/mmcblk0 PCB`
RES=`ntx_hwconfig -s -p /dev/mmcblk0 DisplayResolution`
case $PCB in
E60610*) echo trilogy;;
E60QB*) echo kraken;;
E606B*) echo kraken;;
E5061*) echo pixie;;
E60Q9*) [ "$RES" == "800x600" ] && echo pika || echo alyssum;;
E606C*) echo dragon;;
E606G*) echo dahlia;;
E606F*) echo phoenix;;
E70Q0*) echo daylight;;
E60QL*) echo star;;
E60QM*) echo snow;;
T60Q0*) echo star;;
*) echo trilogy;;
esac
The "pika" is the "Touch 2" and the "alyssum" is the "Glo HD".
Looks like there are three ids that could be used. From that, I'd use either the model id number (in the version file), or the USB product id (same as the calibre driver). The PCB identifier needs extra info and both the others can be access from a PC. But personally, I'd just present a list of model names and let the user select the one they want.