Thread: Retrieve Mark model number via bash
View Single Post
Old 06-21-2017, 08:22 PM   #8
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Aren't you contradicting yourself? The libnickel files are identical, but the keyboard layouts in the same location but are different? I'm not sure how that is possible. But, I just looked at the current patch file, and it does have separate patches for the models with instructions to only patch one.

You shouldn't be creating copies of libnickel and distributing them. These contain proprietary software and hence you would be breaking copyright and licenses. Creating a patch method that can be run against the downloaded firmware update file is probably what you should do. And if you are going to identify the device, then identify them by the model names or number. ie. Show "Glo HD", not "Mark 6". It is clearer to most users, and if there is a difference between keyboards in a particular mark, then you will be covered.
davidfor is offline   Reply With Quote