First, Conal, the boxes are due to the theme I’m using, apparently list items are boxed. I don’t like it either and I’ll try to get around modifying the theme.

Twan, I’ve now added a preview plugin for wordpress. It seems to work quite well and hopefully it’ll make it easier to avoid some of editing problems I’ve seen in comments lately.

parseHex = hexStr2Int <$> many1 hexDigit
parseAddress = Address <$> parseHex <* char '-' <*> parseHex
parseDevice  = Device  <$> parseHex <* char ':' <*> parseHex

You can also simplify things a bit more by combining hexStr2Int <$> many1 hexDigit into a function, then you could say:
parseHex = hexStr2Int many1 hexDigit
parseAddress = Address parseHex <* char ‘-’ <> parseHex
parseDevice = Device parseHex < char ‘:’ <*> parseHex

Also, in cA, should there be a case for character other than ‘p’ or ’s’? Otherwise the program could fail with a pattern match error.

Some much smaller points:

• The pattern (== c) <$> anyChar (nicely written, btw) arises three times, so it might merit a name.
• Similarly for hexStr2Int <$> many1 hexDigit, especially when you rewrite f <$> (a <* b) to (f <$> a) <* b.
• The pattern (a <* char ' ') <*> b comes up a lot. How about naming it also, with a nice infix op, say a <#> b?
• The cA definition could use pattern matching instead (e.g., cA 'p' = Private and cA 's' = Shared).
• Some of your parens are unnecessary (3rd line of parseDevice and last of parseRegion), since application binds more tightly than infix ops.