Thread: Firmware 3.12.1
View Single Post
Old 02-07-2015, 08:09 PM   #27
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
Quote:
Originally Posted by tshering View Post
Another (maybe not so) interesting thing is the mention of the device code names alyssum and pika.
I think the interesting thing is the code in kobo_config.sh:

Code:
E60Q9*) [ "$RES" == "800x600" ] && echo pika || echo alyssum;;
That suggests the pika has resolution of 800x600 but otherwise the same hardware as the alyssum. And the only reason I can think of to make an 800x600 device now is if the screen was smaller. That makes me wonder if the pika is a 5" device to replace the Mini and the alyssum is a 6" to replace the Touch, Glo or Aura. Or maybe all of them.

There isn't much evidence in libnickel to suggest which way they are going.
davidfor is offline   Reply With Quote