Older blog entries for Pizza (starting at number 130)

Linux wifi driver hackery, yay

Since it's still a little too chilly outside for me to take apart my car to replace a defective seatbelt buckle, it's time for a writeup on what I've been up to with my wifi driver hacking.

First, the venerable . For some reason, I keep being surprised at the amount of major surgery between the releases. Since my last posting to linux-wireless, there's been a lot of work:

• Completely rewrote BSS join logic -- IBSS now works!
• Respect TKIP/CCMP group key rx sequence counter
• Improved 802.11g (ERP) coexistence
• Eliminated callback function pointer structures
• Detect CW1160/CW1260 chips (fw load is different though)
• Greatly simpified BSS loss detection
• Fixed deadlocks and/or OOPSen when hot-unplugging non-idle devices
• Pulled support for Sagrad SDIO modules into a separate module that provides the appropriate platform data
• Simplified Beacon filter configuration
• Many, many, many checkpatch-suggested cleanups

I'll probably prepare another upstream submission this weekend, seeing that the driver is now handling everything I'm throwing at it. Finishing CW1260 support needs to wait until I have hardware to test aginst.

Next, I've also spent time on the rt2800usb driver, adding the ability to write changes back to the eeprom and embedded eFuses

. This lets folks update the production data baked into the module at manufacture time, which is occasionally necessary when your module vendor sends you seven hundred modules with a single bit flipped that breaks a legacy product's driver. As an aside, Ralink's official drivers are... painful, to say the least. But kudos to Ralink for maintaining them!

Finally, I started adding support for my employer's STLC4560-based modules to the p54 driver. They come in both SPI and SDIO variants, and have an onboard EEPROM for storing the Production Data. The existing p54spi driver is hardwired to have the PDA loaded from userspace, and there's no support for SDIO devices at all. This is a lower-priority project, but it is nice to be working with the venerable NWN/Intersil/GSV/Conexant/ST 'ARM MAC' again.

Syndicated 2013-03-02 13:15:16 from Solomon Peachy

Gah, Another youtube posted in the recentlog, breaking it thanks to illegal HTML syntax. According to the w3c validator:

Error Line 15, Column 228: Self-closing syntax (/>) used on a non-void HTML element. Ignoring the slash and treating as a start tag.


<iframe allowfullscreen="" frameborder="0" height="315" src="http://www.youtube.com/embed/DR_wX0EwOMM" width="420"/>

Domain registrar recommendations?

In a couple of months, one of my domains is up for renewal. I've been using Dotster for years now, ever since I ran screaming from Verisign nee Network Solutions back in the day, but my eye is wandering.

Mainly because Dotster does not, nor does it have any plans to, support DNSSEC and IPv6 glue records.

If this goes well, then I'll be moving the rest over as they eventually expire.

Syndicated 2013-02-14 03:27:43 from Solomon Peachy

Sunday Hackery

Faced with no getting-my-hands-dirty offline projects today, I decided to spend some time on various F/OSS projects that I've neglected as of late.

The morning started with a flurry CW1200 driver hacking; this time focusing on simplifying its interrupt handling. In the process I eliminated two more compile options and three bus-level virtual functions. As nice as it is to write code, it's even nicer when you delete it without any loss of functionality!

After that, I put my money where my mough was and wrote a systemd unit file for Photo Organizer's background workers. For years I've been using screen and a sudo-driven cmdline to fire them off, because I could never come up with a reliable (and portable) init script to do the trick. No longer. As an aside, systemd is brilliantly put together and worlds beyond anything that's come before. It JustWorks(tm).

Then I pulled out my notes and turned my attention to Gutenprint. The Kodak 1400's unexpected complications derailed my plans a bit, but there were still three related printers whose spool formats I'd decoded -- The Kodak 8500, the Mitsubishi CP3020D/DU/DE, and the Mitsubishi CP3020DA/DAE. They are now all supported by Gutenprint, and awaiting testing. The latter two are the ones I'm most concerned with, as I took a few liberties with the spool format.

Basically, the Mitsubishi-branded printers don't spool the data linearly into the printer; they basically write the color-interleaved data in backward chunks. Consequently, the printer can't start printing until all the data is received. To simplify things, I'm sending the data linearly in one big chunk. Hopefully it will work. We'll find out.

On that note, if there's someone out there with one or more of these printers, care to help out? Either by doing some test prints for me, or better yet, sending me the printers? :)

... and the day is far from over.

Syndicated 2013-01-27 21:06:45 from Solomon Peachy

Okay... this is certainly strange..

Date: Tue, 22 Jan 2013 20:49:36 -0500

From: Jay Ronkonkoma 

To: undisclosed-recipients: ;

Subject: Thank You for your hard work


I'm a big fan of your work on Wireshark.  I was wondering what else you had

going on,  what you were doing that was new,  anything I could read would

be greatly appreciated.



Also, if you have the time and inclination.  please mail a postcard to my

daughter Amanda.  She would love to get a little post card from you.  she

is now 7 going on 15 if you know what I mean.

I would appreciate it, and I know she would love it.  If you don't I

appreciate your time


Amanda Elia

[[ address snipped ]]

Ronkonkoma, NY 11779


Humbly,


Jay Elia

I can't help but think this a soliticitation for highly illegal
activities, if you know what I mean.

It's also been something like six years since my last contribution to
Wireshark, so it would seem someone's busy harvesting addresses from
old commit logs or somesuch.

EDIT: I've reported this email to google via gmail's abuse form.
Going to pass this on to the feds too, once I figure out how to do that.

EDIT2: I've reported this to the feds.

EDIT3: Two others have told me they've received this too.

Syndicated 2013-01-23 02:34:48 from Solomon Peachy

Success with the Kodak Professional 1400

About a week ago a massive box was left on my doorstep containing a lightly-used Kodak 1400 large-format dye-sublimation printer. Lightly used to the grand total of a whopping 72 prints, according to the self-test page.

Unfortunately, my elation turned sour when I discovered that I couldn't just dump the raw spool file to the printer. Firing up a USB sniffer under WinXP, I discovered that the to-the-printer protocol bore little resemblance to the spool file -- even the image data itself used a different format. To top it all off, the printer needed intelligent buffering.

So, armed with the USB sniffer output, I heavily modified the spooler I wrote for the Canon SELPHY printers. Last night, I achieved success, and succesfully printed the WinXP test page I'd previously generated, but also an image printed using gutenprint.

The Kodak 805 printer that replaced this one probably needs a similar treatment (given that it uses the same spool file format) but unless someone sends me a printer (or cash) I won't be able to test that theory out.

I still have to generate another couple of test prints under WinXP to decode two remaining protocol options, but other than that, the Kodak 1400 printer is now usable under Linux!

Oh, this is the first image I printed on this thing via Gutenprint. I wish I could say it was something I took.

Syndicated 2013-01-20 13:38:44 from Solomon Peachy

More driver hackery

This morning, I submitted the third pass at the CW1200 WLAN driver to the linux-wireless list. The changelog is too long to list here, but the bulk of the changes were teased from a code dump that Sony released. It seems they went through much the same pain as I did, and of course none of the changes made it upstream.

Aside from the Sony changes, the single biggest change was a rebalancing of the tx/rx handling, so that it's now considerably fairer. Of course, there was the usual pile of small changes, including a fix for an OOPS triggered by the broken IBSS code. It's still broken, but at least it's not crashing anything now.

We'll see where v3 goes. Hopefully merged into linux-next, or barring that some meaningful feedback on what I need to do next.

In other news, Before the new year I added support to Gutenprint for the Kodak 9810 dyseub printer. None of the code's been committed yet, but there's no real rush. I'm now waiting on a Kodak 1400 printer to show up -- Once I've verified my core gutenprint changes are sound and that printer works, I'll commit everything, marking the untested models as experimental.

Then I'll tackle the Kodak 8500 and the Mitsubishi CP3020D/CP3020DA, not that I'll be able to test those either.. Afterwards, I'll see about the more modern Mitsubishi printers if I'm feeling so inclined.

I really need to start getting rid of this pile of Canon dyseub printers. Maybe four, instead of twelve. At least the incoming Kodak 1400 is a large-format model!

Syndicated 2013-01-13 03:10:34 from Solomon Peachy

CSS hackery

One of the tasks I got up to during my recent "vacation" was the first real hacking on the code powering my photo site in more than a year. This time, the changes are mostly cosmetic in nature. I've been removing javascript/DOM hacks in favor of CSS3 to style the buttons, checkboxes/selections.

The result is far simpler markup and faster page loads because there's no javascript rewriting the page on the fly. In fact, the only javascript present now is the code that inverts the image selection, and even that's far simpler because it just walks the list of checkboxes and toggles them.

I'm also giving attention to the layout and especially element spacing; trying to generally improve the intangible "feel" of the site through subtle tweaks that make things much more visually pleasing.

The goal here is to clean out as much legacy cruft as possible, so I can more easily make more complex (but necessary) UI changes. There are still too many tables used for layout/formatting; I'll be trying to eliminate those next.

I'm back to working on this thing for my sake, solving my own needs, making it into something I want to keep on using, and I must say it's a nice change. Yay for (useful) productivity!

Syndicated 2013-01-09 04:44:55 from Solomon Peachy

More reverse engineering goodness

I decided to make a sweep of it and decode the raw spool formats for the remaining "Professional" Kodak photo printers, the 8500 and 9810. This means that all of Kodak's professional dyesub printers will be supported, save for the long-since-discontinued ML-500.

But I digress. It turns out the 8500 is essentially a rebadged/tweaked Mitsubishi CP3020D, albeit without 8x12 support and a third variation of the Mitsubishi block-chunked image format -- packed BGR data, sent in one ginormous data block but wrapped in the "traditional' 3020D control blocks. That will require no changes to gutenprint to support, so I'll probably implement support for the 8500 before the CP3020D/DA models it's based on.

Meanwhile, The 9810 is very different from the other Kodak models. It uses a command-stream type of format that's on the verbose side but is otherwise well-structured, with the raw RGB data being sent in a plane-interleaved fashion. Supporting it will require no core changes either.

so, this is my plan of attack over the next couple of days:

• Kodak 9810
• Kodak 8500
• Mitsubishi CP3020D
• Mitsubishi CP3020DA
• Other (current!) Mitsubishi models?

Anyway. Time to go to bed.

Syndicated 2012-12-26 04:23:58 from Solomon Peachy

Another two Kodak printers supported..

Just added support to Gutenprint for the Kodak 605 and 805 dyesub printers. They were mostly the same as the 6800 and 1400 (respectively) they replaced.

I've also reverse-engineered the raw dump formats of the Mitsubishi CP3020D and the CP3020DA 8x10 dyesub printers. They use a somewhat convoluted block-oriented format, with the former using CMY-based plane interleaving and the latter using RGB-based scanline interleaving. To add joy to the mix, the blocks are sent to the printer in reverse order (bottom-up), but within each block the scanlines are top-down.

Once the Kodak 1400/805/6800/6850/605 support is reviewed and committed into Gutenprint, I'll start working on the low-level changes necessary to support these Mitsubishi printers.

Maybe a grateful user will mail one of them to me in thanks? (hint hint)

Syndicated 2012-12-25 17:08:56 from Solomon Peachy