Thread: Firmware 2.8.1 ?
View Single Post
Old 07-28-2013, 10:00 PM   #324
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 PeterT View Post
It has been since day 1. All you need do is to select the checkbox "Attempt to support newer firmware" in the driver configuration.

Trust me, if ever the time comes that a Kobo uograde is NOT compatible, someone will have posted big warnings here cautioning all of the incompatibility.
And to reiterate what Peter said: yes it is, you just needed to check the option. I have a posted on this on the first page of the thread. In any case, calibre 0.9.41 was released on the weekend and it will recognise 2.8.1 as an OK firmware.

And so people know.

Kobo do have a beta firmware program. I am part of that. When a new beta comes out, testing calibre with it is the third thing I do. That's after checking to see if they have fixed any of my "favourite" bugs and seeing what new things they have added. If I find something wrong, I fix it as quickly as I can or when I think the change has settled in the firmware. Same goes with new things. Happily, most of the changes Kobo make don't break the calibre driver. In nearly all cases it will work unchanged and any changes needed are to take advantage of something new.

This means I usually know if there is going to be a problem when the firmware is released. And I usually have code ready to be checked in when it is. Sometimes I will check the code in before the firmware release if I don't think that will cause other problems. I'll admit that one of the problems I want to avoid is answering the question "Calibre supports firmware x, where is it?". And I especially don't want to answer that question if there is a real change. Which is why the code changes for the next firmware won't be checked in until the firmware is released
davidfor is offline   Reply With Quote