Dossy's Blog

Apparently, South African Airways runs some kind of Linux for their in-flight entertainment system.

Of course, on the leg of the trip from New York to Senegal, the flight staff kept rebooting the system trying to get it to work, with very little luck. Most of the time we just stared at the Linux boot process hanging, trying to talk to the NFS server. Fortunately, they got it working for the Senegal to South Africa leg of the trip.

Tags: South African Airways, Linux, fail

I love problem solving and puzzles. My friend Christina brought me back a fun one from her trip to Mongolia. Here it is, solved:

Apparently this puzzle type is what Stewart Coffin calls “Locked Nest.”

It may not look like much, but the challenge is to assemble it from a completely disassembled state. It’s not only geometrically challenging, having to visualize the pieces in their final states, but physically challenging, having to hold the thing together as you put it together. Several times, while I was working on the puzzle, a pin would slide out or a rod would be out of alignment and the pin would miss it.

This is definitely a puzzle I’ll enjoy solving many times over. It’s quite challenging.

Tags: Mongolian, puzzle, Stewart Coffin

So, I have a TiVo Series 2 stand-alone DVR with a Product Lifetime subscription. For years, I’ve had it connected to the home network using a Linksys WUSB11 wireless network adapter, but it finally died. I went and grabbed a Linksys WUSB54G as a replacement, but found out that the TiVo doesn’t support it. No problem, I know the TiVo runs Linux and there’s plenty of documentation on how to “hack” the TiVo so I can load my own kernel modules on it, etc.

It turns out that the Linksys WUSB54G v4 uses the Ralink 2570 chipset. Fortunately, there’s been effort on native Linux drivers for the Ralink family of wireless chipsets. The hurdle, of course, is that the TiVo’s MIPS R5432 is big-endian, so it presents a bit of a challenge porting the driver to the TiVo.

Working off the latest code for the legacy rt2570 driver from CVS, I’ve gotten it to compile using TiVo’s Linux 2.4.20 kernel. Loading the module, however, results in this:

rt2570: init
usb.c: registered new driver rt2570
rt2570: idVendor = 0x13b1, idProduct = 0xd
rt2570: idVendor = 0x13b1, idProduct = 0xd
rt2570: using permanent MAC addr
rt2570: Active MAC addr: 00:12:17:89:f5:02.
rt2570: driver version 1.0.0
Unaligned Access to 0x80230b2b in kernel mode at 0xc0217be4
Unaligned Access to 0x80230b2d in kernel mode at 0xc0217c04
Unaligned Access to 0x80357076 in kernel mode at 0xc021b3dc
Unaligned Access to 0x80357076 in kernel mode at 0xc021b408
Unaligned Access to 0x80357076 in kernel mode at 0xc021dc2c
Unaligned Access to 0x80357076 in kernel mode at 0xc021dc08
Unaligned Access to 0x80357076 in kernel mode at 0xc021cd8c
Unaligned Access to 0x80230f47 in kernel mode at 0xc0217be4
Unaligned Access to 0x80230f49 in kernel mode at 0xc0217c04
Unaligned Access to 0x80231155 in kernel mode at 0xc0217be4
Unaligned Access to 0x80231157 in kernel mode at 0xc0217c04

So, now I get to go fishing through /proc/ksyms and try to fix up all these unaligned access errors. Hopefully, I’ll be able to get through all of this and get the driver working.

Anyone out there have experience porting Linux device drivers like this? Got any tips or techniques that might help me? I’d really love any help I can get …

Update: I’m posting my debugging progress in a rt2×00 forum thread. Given enough eyeballs, all bugs are shallow, right?

Update: I’ve gotten it working! I’ve addressed the majority of the unaligned access traps and I can now use my WUSB54G as a wireless NIC on my TiVo! Here’s a patch against rt2570-cvs-2008102616 of the driver and the corresponding kernel module binary:

• rt2570-tivo-mips.patch
• rt2570.o.gz (1.42 MB)
  MD5: 64605e019929db714d583d160a6b513c

If you have a SA2 TiVo and want to use a Linksys WUSB54G as your wireless NIC, this driver is what you want. It works for me, anyway!

Tags: Linux, TiVo, open source, hacking, Linksys WUSB54G, Ralink 2570

I’m selling a BlackBerry 8830 World Edition Verizon phone on eBay for a friend. The auction will end next Friday, February 22nd. If you’re interested in it or know someone who is, please go and bid on it.

After not being able to get data services on my Treo 650 last week, I finally had enough. It was over two years old and I was eligible for an “upgrade.” It was time to say goodbye to Palm and its aging hardware and operating system and move on to something more modern … or at least, switch to a product from a company that’s a little more commercially viable. I considered the Apple iPhone, but just can’t bring myself to pay the ridiculous “Apple Tax”–the extra money you pay for Apple’s fancy design. When a carrier offers the iPhone for $99, I might consider them.

What at&t was offering for $99 this time around was the Blackberry Curve 8310 [at Amazon]. So, on February 4th, my wife and I went to the Willowbrook Mall at&t store and bought them. I also picked up an Aliph Jawbone [at Amazon] Bluetooth headset for myself and she chose the Motorola H12 [at Newegg] Bluetooth headset. We could have saved some money ordering it all online, but there’s something to be said for immediate gratification, being able to walk out of the store an hour or two later with everything just working. However, I did end up ordering two Sandisk 4GB MicroSDHC memory cards for the phones from Amazon.

I’m not going to try and do a full review of these products as there are already plenty out there if you search for them. What I will do is list the things that I discovered, especially stuff that surprised or disappointed me. It’s going to be completely subjective and folks may not agree with what I point out as being important, but they’re important to me.

(1) The 8310 has GPS which is very cool, but TeleNav’s service is $9.99/mo for unlimited routes. Ouch. Still, the software and service seems excellent so far and it’s still cheaper and more convenient than buying a dedicated GPS unit.

(2) The 8310 has GPS while the 8320 has 802.11b/g Wi-Fi. Yeah, I really would have liked my new phone to have Wi-Fi, but in reality, having GPS will be far more useful for me.

(3) The Blackberry OS 4.2 that currently ships with the device doesn’t let you record video. Luckily, RIM is working on their next upgrade, OS 4.5 (formerly referred to as OS 4.3.1, apparently renumbered by marketing) that will. I just hope they don’t keep slipping the anticipated release date over and over. Anyone know how to get into their beta program? I’d love to play with the beta release.

(4) Even though the 8310 has GPS, it appears that pictures taken with its camera do not store the GPS location in the image’s EXIF data. Again, not a big deal but something that I had expected and it not being implemented surprised me.

(5) The push-email sync. delay is a lot longer than I expected. My guess is that the Blackberry Internet Service doesn’t poll my IMAP mailboxes as frequently as I’d hoped, because even manually performing a “Reconcile Now” doesn’t seem to help. I’m guessing they only poll every 10-20 minutes which isn’t that bad, but not having a proper manual “sync now” that triggers the back-end poll is a let-down.

(6) When paired with a Bluetooth headset, answering the call with the green phone button defaults to the headset. I expected that answering the call by pressing a button on the phone would default to activating the handset. If I wanted to answer the call on my headset, I would have used the headset to pick up the call. This matters because I often have my phone in my pocket but leave my Bluetooth headset in my jacket pocket; I only wear it when I’m actually out and about. So, when I receive a call, I’ll grab my phone and answer it but the phone sends the call to the headset–argh! I then have to hit the menu button and select “Activate handset”, or press the $/Speaker button to use speakerphone, to actually talk on the phone. At the very least, this needs to be a configurable option in the phone application, whether to answer the call using the Bluetooth headset or on the handset.

(7) The Jawbone is an awesome headset. The noise cancellation really works well. It’s really comfortable to wear; it feels lighter on the ear than it actually is. But, it’s butt-ugly. I mean, it’s embarassing to wear this thing in public, it’s so ugly. When you buy the Jawbone, you’re definitely not buying it for the looks, that’s for sure. But, if you spend a lot of time talking on your cellphone, especially in public places or, like me, in the car with the window open, this headset will not let you down.

(8) On the other extreme, the Motorola H12 is gorgeous. It is small, lightweight and aesthetically pleasing. Even the charging base looks great on a desk and the use of magnets to attach the headset to the charging contacts on the base make my inner geek go “squee!” The sound cancellation on the H12 is adequate, but I’m not convinced it’s nearly as good as the Jawbone. However, where the H12 falls short in technical quality compared to the Jawbone, it more than makes up for it in sexy. I’m actually tempted to return my Jawbone in exchange for another H12, for just this reason.

That’s it for now. I’m anxiously awaiting the Blackberry OS 4.5 and what improvements it will bring. I’ll post an update once it arrives.

Do you have a Blackberry? Have any tips for me? Your favorite applications that you think I might enjoy? Any cool undocumented features or shortcuts that you’d like to share? Please tell me about them in the comments here.

Tags: Blackberry Curve 8310, Aliph Jawbone, Motorola H12, Bluetooth, TeleNav, GPS