pali

Hi! I have there printer labeled `brother model HL-11`. It should be `Brother HL-1112` and after running EXECUTE PRTCONFIG command (found in https://github.com/filisko/hl1110-utility-tool) I get printed test page with information:...

When I connect it via USB, then lpinfo identify it as: ``` $ sudo lpinfo --include-schemes usb -l -v Device: uri = usb://Brother/HL-1110%20series?serial=XXX class = direct info = Brother HL-1110...

@pdewacht Could you please include this printer to `brlaser.drv.in` file so it would be automatically detected by cups?

Please note that newly released specification is incomplete. There is e.g. missing important information about TexFAT.

Nope, I have not implemented it. I have no motivation to use such rubbish like exfat which is moreover step backward from FAT32. And due to patents problems I doubt...

Problem with maintainers? Why? I fully understand maintainers that do not want to include exfat support due to above patent problems. As said, they really do not want to have...

Look, you cannot use something which is disallowed by law. And you said "problem with maintainers" just because they decided not to break low... Nope, this is not a problem....

Yes, it is still an issue. Blame to distributions which stopping shipping the only suitable libusb library for flashing or blame to libusb-1.0 developers who fully ignore this issue... https://sourceforge.net/p/libusb/mailman/message/34985373/...

Ehm... why bundle in upstream project?? It is up to downstream distribution to distribute package software with all dependences so it would work. It is not responsibility of upstream projects,...

So now every software needs to start bundling working version of libusb, just because distributions are unable to do it? Ridiculous! So blame to distributions if they are dropping old...