Well, the discussion about SystemStarter seems to have died
down, I am not sure if anything was exactly resolved, but I
think everyone has managed to think about it a bit, and
probably has realized there is some margin on all sides. I
think that I am going to look at the code I have written,
decide if any of it is at all useful in anything resembling
the scheme on the table, and if so isolate that and make a
patch. I am not optimistic about that, but this was kind of a
side project anyway, I just wanted to get it working for /
dev/random. I was doing this for a few days while I was
thinking about the best way to implement some of the entropy
gathering, I think I will go back to that.
I tried to get FAQ-O-Matic to build on any of the machines I
have CGI access on, it did not seem to like them. Maybe I
should just get a sourceforge project, they probably have
machines that are better setup for things like this. Or I
could setup another maachine, but RPI seems to have
completely revised some of the firewall rules, and it might
be a real pain to get a new IP through it.
I spent a few hours playing with Larry's T20 tring to
get its ethernet card (3com MiniPCI) up and running under
linux. This makes no real sense to me, since I barely use
intel hardware, I don't use any 3com hardware, and have not
used linux in a year or so. I had no luck. A friend had a
written a patch for FreeBSD. He told me I would have to map
the rom and add the card id to the linux driver. I definately
did the later correctly, not so sure about the former. He
told me I should just look at the docs for the 905B
otherwise. That does me very little good, since the driver I
was patching already works with the 905B ;-) He also was
supposed to submit-pr his driver, but I don't think he did...
So I have two lines of notes consisting of addresses, and a
linux driver that works for similar cards. I am not about to
go poking around, since:
- I don't know how to twiddle pci from userspace under
linux
- I probably would make assumptions about how things work
based on my experience in the big-endian world
- I know that accessing the eeprom wrong can make the card
unusable (though it can be fixed if you know what you are
doing)
- The person who go tthe FreeBSD driver working has been
writing 3com driver code for the last year, and was very
familiar with 3com chips, I am not, and this card has no
documentation
Oh well, I gave it my best shot. Given good documentation and
a little while I could do it, given a few days and
documentation, it is probably best left to someone who has
some familiarity with it.