Monthly Archive for April, 2007

I’ve just built a 2.6.21 kernel for my machine, only to realize that the machine doesn’t behave like some other similar (if not identical) MacBook Pro do.

Facts:

• the keyboard does not need the HID_QUIRK_POWERBOOK_ISO_KEYBOARD quirk, otherwise the @ and < keys are inverted.
• on the ALSA side, the macbook_pro_v2_pin_configs config does not work; the headphones work but not the speakers. I’m using the macmini_pin_configs config from the 2.6.20 mactel-linux patches which does work fine (and is identical to the macbook_pin_configs config in the 2.6.21 kernel).

So, now I’m really confused. A colleague here has got the exact same machine, except he bought it in mid-february and I bought mine back in november (the day after they were announced by Apple, so my machine is one of the “very first” Core2 Duo MacBook Pro). Either there has been a new hardware revision, or there’s something weird happening. I’m running an x86-64 kernel and my colleague is running an i386 kernel, but I really can’t believe it makes any difference at all.

I guess I’ll have to find out what’s going on …

I am currently going through the SANE bugs reported on bugs.d.o. There are quite a few of them, and verifying them already takes a long, long time; fixing them is another story entirely, given I own none of the affected scanners or platforms.

I’ll be going through the bugs this week-end, re-reading the logs, tagging/retitling as needed so hopefully the list will be easier to read.

If you have – or are affected by – an open bug against SANE, please try to reproduce the bug on an up-to-date unstable system. I’ll be uploading a CVS snapshot to unstable today for that purpose.

SANE is a complex piece of software that is best maintained in a team, if only because there’s so much hardware involved that the more maintainers you have, the more different hardware you can have too. If you have a scanner, have some knowledge about USB, shared libraries, GTK among other things and want to help, mail me and tell me what you can/want to do. Some knowledge about SCSI can help too, though SCSI scanners aren’t exactly mainstream anymore.

I currently own only 3 scanners, one old SCSI scanner and a pair of nearly identical USB scanners; so that really makes 2 scanners.

If you have some scanners lying around that you don’t use anymore, I (and the SANE developers too) could probably use them. I’m primarily interested in any scanner that is involved in one of the bugs currently open against SANE. I’m also looking for a scanner supported by the epson backend (the Epson scanners I have are supported by the snapscan backend).

Now, back to these damn bugs.