[Yaird-devel] Bug#584565: Bug#584565: Bug#584565: Bug#584565: [PATCH] enable yaird for kernel.org 2.6.33.4

[Nils Radtke]

  Hi Jonas,

On Tue 2010-06-08 @ 02-01-54PM +0200, Jonas Smedegaard wrote: 
# >A simple
# > touch /lib/modules/2.6.33.4/modules.{pci,usb}map
# >did work for me..
# 
# Hmm, interesting.  Perhaps then simply loosening up the code to skip
# parsing that file if unavailable is the way to go.  Need to
# investigate closer to ensure not loosing stabiliy or features by
# such approach.
I'd say, it should work because it has to parse the /sys fs anyway (or
does it shortcut when there's info available from the maps?
If so, then loosening up is the way I'd go, as the non-existence isn't
a crucial precondition but a way to get a hint.

# ># But I am a bit suspicious about the devices that you ignore - could
# ># you perhaps elaborate more on that, to help ensure that they are
# ># universally sane to ignore?
# >Hm, I'd say, I just ignore path endings that aren't (at least for me)
# >any devices.. As I said, no warranty that my patches will work w/o
# >flaws for anyone else..
# 
# Fair enough.  I will then investigate closer before applying to
# official yaird, to ensure not risking stability.
My approach was: look out for devices I have, what is present in 
sysfs and which matches yaird depends on. Then I used the match
loop and combined those matches w/ what is available in sysfs. 
That way it seemed quite clear which devices and paths are the ones
yaird is depending on (locally, on my setup). There were symlinks
and location changes in the sysfs, but - obviously - the devices
are there and yaird had to be made to find them w/ the latest kernel. 
The rest was adaptation of matches and ignores within the loop.

# I sure appreciate your sharing your hacks, even if that's all you want.
I'm happy if someone else may make use of them. 
 
# Trying to enroll you in the greater task of maintaining yaird in
# general is clearly abuse of your friendly and limited filing a
# bugreport - hope you dont mind that :-)
Never mind, thanks for the idea, Jonas. :)
 
# I would be happy to guide you with both git and Alioth.  If
# interested, please subscribe to the mailinglist at
# http://lists.alioth.debian.org/mailman/listinfo/yaird-devel and
# let's discuss further there.
 
# I am patient.  Even with years between your contributions, I would
# still prefer that you work in the main VCS than passing the results
# as diffs to the BTS.
*g okidoki

# I have made little progress since then, but do not consider it dead.
# YMMV.
Hm, my impression is it'd be interesting to re-implement yaird using
an abstraction layer of some sort to alleviate the tedious and returning
burden of kernel adaption.. some unit-testing to ensure backward compat
might ease the change..

    Cheers,

            Nils