1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
lssbus:
So, I got bored. How many pieces of code have had this as an inspiration, I wonder?
Well, at least this one does. I've been happy with what Kudzu does, but I wished it
was a little simpler (and a little faster), something like lspci. Now, just like
kudzu, lssbus is limited to detecting the hardware devices it knows about, but in
this case, it covers everything that most people would care about.
This program doesn't really have any instructions. To build it, run "make". The only
real prerequisite I can think of is that you have a working compiler and the linux
kernel headers. Oh yeah, you also need to be on a sparc. If you're trying to run this
on any other architecture, stop and think, why am I trying to probe a non-existant
sbus? I could have coded in a restriction for sparc, but quite frankly, if you're
stupid enough to try and build/execute this code on a non-sparc machine, you deserve
whatever errors you get.
This code is licensed under the GPL, included in the "COPYING" file which should be
right next to this "README".
It lives at http://people.redhat.com/tcallawa/lssbus.
If you liked this application, or found it useful, you can repay the work I put into
it (admittedly, only a few hours or so between doing about 10 other things), by doing
the following:
Step 1: Stop reading slashdot. If you don't read slashdot, stop reading the register.
If you don't read either of those, stop reading OSnews. If you're not reading any of
these tabloids, skip to step 2.
Step 2: Go to lwn.net and purchase a subscription. Trust me on this one, the news they
provide is worth the money. Its $5.00 US a month, most people spend more on fast food
each week. http://lwn.net/subscribe/
Step 3: Profit.
If you'd like to improve, patch, alter, abuse, mutilate, bend, or vibrate the code for
lssbus, feel free to do so. You won't hurt my feelings. I know the code is far from
optimal, and tested patches will be happily accepted. Make sure all patches are in
unified diff format (diff -u). Its just polite, you know.
- tom "spot" callaway <tcallawa@redhat.com>, Wed April 7, 2004
|
