Slaxer_Pup 4.12 solid and stable non woof build
The 'trick' I used for putty, was to let it configure itself(which is for the non-gtk build), but then compiled it using the Makefile.gtk and then used the normal install routine(for the non-gtk build) which installs the same objects.
A note to Joe, I am getting pretty close to having an installable i586-kiss-linux, and I have some special sources I'll be makign available. Among them is a highly-patdched, one-of-a-kind gtk-1.2 like nobody else has, with a nicely modified file-selector and fixes from about 10 distros.
i586-kiss-linux is being built *entirely* using scr2pkg scripts which are arch-agnostic. So once I have all the scripts done, a whole distro for another arch can be built pretty-much automatically. And, since src2pkg can now automatically split packages (as well as compress the bins and do other tiny-ness-related things), it's gonna be a snap to produce 'tight' packages by the hordes!
I have an iMac, so I'll probably run off a ppc port first, then I'll work on the port for the loongson processor (since I have a gdium and promised to create a port). Raffy is checking on some ARM-based netbooks also, and I hope to get one and create that port also. What this all means is having a common base for several significant arches, from which to build one or more varieties of 'compact' distros.
A note to Joe, I am getting pretty close to having an installable i586-kiss-linux, and I have some special sources I'll be makign available. Among them is a highly-patdched, one-of-a-kind gtk-1.2 like nobody else has, with a nicely modified file-selector and fixes from about 10 distros.
i586-kiss-linux is being built *entirely* using scr2pkg scripts which are arch-agnostic. So once I have all the scripts done, a whole distro for another arch can be built pretty-much automatically. And, since src2pkg can now automatically split packages (as well as compress the bins and do other tiny-ness-related things), it's gonna be a snap to produce 'tight' packages by the hordes!
I have an iMac, so I'll probably run off a ppc port first, then I'll work on the port for the loongson processor (since I have a gdium and promised to create a port). Raffy is checking on some ARM-based netbooks also, and I hope to get one and create that port also. What this all means is having a common base for several significant arches, from which to build one or more varieties of 'compact' distros.
Hey Gilbert
when you finish you already know I want a copy
thanks for providing the scripts
I want to do a how to about compiling some simple apps with src2pkg
to get people started here in the puppy camp
I know it will even be easier when the pet package splitting is official I have a test copy
I really need the *tgz to split packages to save time that would ROCK!
always thankful for your help and work
--------------------------------------------------------------------
ahhh Gilbert just to confirm your build script does work on slaxer_pup
I had to test it on a clean install to be sure all the depends were met
using this script attached that amigo provided will auto build the package
you'll have to add in the icons and desktop manually for this one
don't build in root make a folder ok
note: most of the time you just need
src2pkg -A -E packagetocompile.bz2
this is an example for advanced users
I need to post some simple builds too
this above package putty is a good example of how to use build scripts so you always build the package correctly in an organized way
so that when a new version comes out you have a perfect record of what needs to be done
Joe
i586-kiss-linux is being built *entirely* using scr2pkg scripts which are arch-agnostic. So once I have all the scripts done, a whole distro for another arch can be built pretty-much automatically
when you finish you already know I want a copy
thanks for providing the scripts
I want to do a how to about compiling some simple apps with src2pkg
to get people started here in the puppy camp
I know it will even be easier when the pet package splitting is official I have a test copy
I really need the *tgz to split packages to save time that would ROCK!
always thankful for your help and work
--------------------------------------------------------------------
ahhh Gilbert just to confirm your build script does work on slaxer_pup
I had to test it on a clean install to be sure all the depends were met
Code: Select all
src2pkg -X putty.src2pkg
you'll have to add in the icons and desktop manually for this one
don't build in root make a folder ok
note: most of the time you just need
src2pkg -A -E packagetocompile.bz2
this is an example for advanced users
I need to post some simple builds too
this above package putty is a good example of how to use build scripts so you always build the package correctly in an organized way
so that when a new version comes out you have a perfect record of what needs to be done
Joe
- Attachments
-
- putty_build_script.tar.gz
- (843 Bytes) Downloaded 417 times
Last edited by big_bass on Wed 02 Dec 2009, 01:52, edited 1 time in total.
Can you let PowerPup know in this thread, when you've done it....I'll be interested too if it'll work on a G3?amigo wrote:I have an iMac, so I'll probably run off a ppc port first
http://www.murga-linux.com/puppy/viewto ... &start=105
thanks, both
Aitch
Yeah, I was out of my depth trying to compile that package. Thanks amigo for explaining how it's done.The 'trick' I used for putty, was to let it configure itself(which is for the non-gtk build), but then compiled it using the Makefile.gtk and then used the normal install routine(for the non-gtk build) which installs the same objects.
I'll stick to fishing in shallower waters for now
Now that's more like it. Back to testing code on hardware. That's a great projectRaffy is checking on some ARM-based netbooks also, and I hope to get one and create that port also.
I've been trying to keep an eye on these ARM-based netbooks but I haven't found any for sale. They promise lower power consumption resulting in less heat and longer running time. I'm eagerly awaiting these beasts. I'll have to ask Raffy what he's found.
@Joe Thanks for the slaxer_pup_updater. Good to have it all in one script.
In case you guys were wondering what I wanted putty for, I've been updating the firmware in a couple of devices with embedded Linux (an ASUS WL-HDD NAS and AP, more info: http://wlhdd.co.uk/wiki/Guide and a Linksys NSLU2 NAS using external disks, more info: http://www.nslu2-linux.org/).
I've got the WL-HDD running Oleg's firmware now and storage is on a Compact Flash card instead of a hard disk. I've installed a few apps including samba and transmission via ipkg.
I've got a few choices of firmware for the NLSU2 (aka 'SLUG'). Right now it's running Unslung firmware but I'm looking into installing Debian on it.
(The OS used on an ARM-based netbook wont be that much different from that running in these devices: the NSLU2 has an ARM Intel XScale CPU, whereas the WL-HDD has a MIPS CPU from Broadcom,)
Paul
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Guys, here's a new nut to crack
It's the driver source code for the VT6655 wireless card in my eBox-2300. I want to use this tiny PC as a file server in my network. The only thing that doesn't work in SlaxerPup is wifi.
According to the download page it is supported by these OS:
Debian Linux, Fedora Core 8.0 Linux, Fedora Core 7.0 Linux, Ubuntu 8.04 LTS, Ubuntu 8.10, Ubuntu 9.04, Ubuntu Linux - pre 8.04, Fedora Core 5.0 Linux, Fedora Core 6.0 Linux, openSuSE Linux 10.3 & earlier versions, Source packages, Fedora Core 4.0 Linux, Fedora Core 3.0 Linux, SuSE Linux Enterprise 11, Fedora Core 9.0 & 10.0, Xandros, Fedora Core 1.0 & 2.0 Linux
So it seems to me it should work with SlaxerPup
I've tried compiling it with src2pkg and manually but get an error:
Can anyone (Joe or amigo ) get this driver to compile?
Here's the source code:
http://www.viaarena.com/Driver/VT6655_L ... 02_x86.rar
EDIT: I was a little too hasty. I'm also missing the sis7019 sound driver. Barry normally has it in puppy. I couldn't get this to compile either [sigh]. This compiling business isn't easy
I'm attaching the sis7019 source.
Paul
It's the driver source code for the VT6655 wireless card in my eBox-2300. I want to use this tiny PC as a file server in my network. The only thing that doesn't work in SlaxerPup is wifi.
According to the download page it is supported by these OS:
Debian Linux, Fedora Core 8.0 Linux, Fedora Core 7.0 Linux, Ubuntu 8.04 LTS, Ubuntu 8.10, Ubuntu 9.04, Ubuntu Linux - pre 8.04, Fedora Core 5.0 Linux, Fedora Core 6.0 Linux, openSuSE Linux 10.3 & earlier versions, Source packages, Fedora Core 4.0 Linux, Fedora Core 3.0 Linux, SuSE Linux Enterprise 11, Fedora Core 9.0 & 10.0, Xandros, Fedora Core 1.0 & 2.0 Linux
So it seems to me it should work with SlaxerPup
I've tried compiling it with src2pkg and manually but get an error:
Code: Select all
# make && make check
Makefile:93: /lib/modules/2.6.27.7/build/.config: No such file or directory
make: *** No rule to make target `/lib/modules/2.6.27.7/build/.config'. Stop.
Here's the source code:
http://www.viaarena.com/Driver/VT6655_L ... 02_x86.rar
EDIT: I was a little too hasty. I'm also missing the sis7019 sound driver. Barry normally has it in puppy. I couldn't get this to compile either [sigh]. This compiling business isn't easy
I'm attaching the sis7019 source.
Paul
- Attachments
-
- sis7019-patched-p212.tar.gz
- (37.9 KiB) Downloaded 418 times
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Yeah, you'll have a lot better luck compiling anything using slack. As far as which version to install -try to match the kernel version as closely as possible with what puppy is using. If you mostly compile software and not kernel modules, then it would be better to match to the glibc version insetad of the kernel.
Hey Paul (pakt)
all compiled well notice that the official 4.12
has these installed
wpa_supplicant-0.5.10
openssl-0.9.8e
they are newer versions than the ones you posted the sources to
so no need to compile those for now
------------------------------
install this package VT6655-driver-v1.20.02-i486-slxr.tar.gz
after installing it gets installed here *if you wanted to double check
/lib/modules/2.6.27.7/kernel/drivers/net/viawget.ko
then run
in the terminal to update your new module
so its added /lib/modules/2.6.27.7/modules.*
I updated the net list for you use this netlist-update-VT6655-i486-slxr.tar.gz
then when you run the connection wizard you'll now see
viawget "pci: VIA Networking Solomon-A/B/G Wireless LAN Adapter Driver"
P.S
*The sources for the audio driver failed I need to get the un patched sources*
keep me updated let me know how it went with those packages
had to rename to tar.gz for the forum to upload it
Joe
all compiled well notice that the official 4.12
has these installed
wpa_supplicant-0.5.10
openssl-0.9.8e
they are newer versions than the ones you posted the sources to
so no need to compile those for now
------------------------------
install this package VT6655-driver-v1.20.02-i486-slxr.tar.gz
after installing it gets installed here *if you wanted to double check
/lib/modules/2.6.27.7/kernel/drivers/net/viawget.ko
then run
Code: Select all
depmod -a
so its added /lib/modules/2.6.27.7/modules.*
I updated the net list for you use this netlist-update-VT6655-i486-slxr.tar.gz
then when you run the connection wizard you'll now see
viawget "pci: VIA Networking Solomon-A/B/G Wireless LAN Adapter Driver"
P.S
*The sources for the audio driver failed I need to get the un patched sources*
keep me updated let me know how it went with those packages
had to rename to tar.gz for the forum to upload it
Joe
- Attachments
-
- VT6655-driver-v1.20.02-i486-slxr.tar.gz
- (116.64 KiB) Downloaded 515 times
-
- netlist-update-VT6655-i486-slxr.tar.gz
- (2.88 KiB) Downloaded 517 times
Last edited by big_bass on Mon 14 Dec 2009, 19:30, edited 2 times in total.
Paul (pakt)
having slackware installed is always a good idea
but its not requiered to compile anything for slaxer_pup
yes, you need the full kernel sources when compiling those drivers
so you wouldn´t have got it to work without them for this job
I made a *.tgz of the sources it will be a few days before I can upload it
its at 170MB compressed over 750MB installed
I usually run USB install for day to day stuff so I had to set up another hard drive install
before I could compile the drivers for you
but I have to have that anyway so it was needed
most of the time you don´t need the kernel sources
installed so to save space I only install them when needed
*typo edit
Joe
Can I assume these drivers need the complete headers to compile?
Would it help if I installed Slackware 12.2 on one of my old PCs should I want to (try to) compile drivers in the future?
having slackware installed is always a good idea
but its not requiered to compile anything for slaxer_pup
yes, you need the full kernel sources when compiling those drivers
so you wouldn´t have got it to work without them for this job
I made a *.tgz of the sources it will be a few days before I can upload it
its at 170MB compressed over 750MB installed
I usually run USB install for day to day stuff so I had to set up another hard drive install
before I could compile the drivers for you
but I have to have that anyway so it was needed
most of the time you don´t need the kernel sources
installed so to save space I only install them when needed
*typo edit
Joe
Last edited by big_bass on Wed 16 Dec 2009, 16:34, edited 1 time in total.
You don't need the compiled sources, you only need them to be configured. Unpack sources, insert your favorite config file, run 'make silentoldconfig' and then run 'make prepare', then the sources can be used or re-packed and installed elsewhere.
I did have a look at these things the other day. The vt6655 compiled without problems. But, the other sources will need to be patched for use with later kernel sources as it searches for 'config.h' which no longer exists in the kernel sources -linking to the 'autoconf.h' should work, or it's pretty easy to change that in the driver sources.
I did have a look at these things the other day. The vt6655 compiled without problems. But, the other sources will need to be patched for use with later kernel sources as it searches for 'config.h' which no longer exists in the kernel sources -linking to the 'autoconf.h' should work, or it's pretty easy to change that in the driver sources.
Joe, I appreciate all the work I put you through. I'll let you know how it goes
I installed Slackware 12.2 on a spare partition I had on an old laptop and was remined of the old days when you spent more time setting up Linux than actually using it. Among other things, the keyboard-chooser was broken, the mouse wheel didn't work and I got nowhere setting up wireless using the network gui. In the end I just opened a terminal and setup wifi using the command line.
(The good thing with this exercise was that it reminded me of how easy it is to setup Puppy )
Another thing I was reminded of was the question of which kernel to use in slackware to make it compatible with SlaxerPup. Two choices: huge.s or hugesmp.s. SlaxerPup has an smp kernel so I assumed I should use hugesmp.s. Then, like amigo, I succeeded in compiling the vt6655 driver but when I tried modprobing it in SlaxerPup, I got an error message. I think it said something about a mismatch - seen it before when attempting to use a module for another kernel.
I re-installed Slackware with the huge.s kernel yesterday but it was just as well that I didn't have time to try compiling vt6655. I doubt if I would have gotten the right module since uname confirmed it isn't an smp kernel. So the question is, is either kernel compatible with the one in SlaxerPup?
Regarding the full kernel sources, wouldn't it be ideal to make an sfs file of them? That would make them nice and portable, be accessible from a frugal installation and not take up any memory, or?
amigo, good info on setting up kernel sources and on patching the audio driver source. I'll check the net first and see if I can find the original or newer audio driver source.
Paul
I installed Slackware 12.2 on a spare partition I had on an old laptop and was remined of the old days when you spent more time setting up Linux than actually using it. Among other things, the keyboard-chooser was broken, the mouse wheel didn't work and I got nowhere setting up wireless using the network gui. In the end I just opened a terminal and setup wifi using the command line.
(The good thing with this exercise was that it reminded me of how easy it is to setup Puppy )
Another thing I was reminded of was the question of which kernel to use in slackware to make it compatible with SlaxerPup. Two choices: huge.s or hugesmp.s. SlaxerPup has an smp kernel so I assumed I should use hugesmp.s. Then, like amigo, I succeeded in compiling the vt6655 driver but when I tried modprobing it in SlaxerPup, I got an error message. I think it said something about a mismatch - seen it before when attempting to use a module for another kernel.
I re-installed Slackware with the huge.s kernel yesterday but it was just as well that I didn't have time to try compiling vt6655. I doubt if I would have gotten the right module since uname confirmed it isn't an smp kernel. So the question is, is either kernel compatible with the one in SlaxerPup?
Regarding the full kernel sources, wouldn't it be ideal to make an sfs file of them? That would make them nice and portable, be accessible from a frugal installation and not take up any memory, or?
amigo, good info on setting up kernel sources and on patching the audio driver source. I'll check the net first and see if I can find the original or newer audio driver source.
Paul
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Guys, I just found these on http://www.tcosproject.org/debian.php:
EDIT: Also found this:http://git.kernel.org/git/?p=linux/kern ... 7072cc2b72
Any good?sis7019-alsa-backport-source (1.0.0-2) - sis7019 ALSA driver for vortex sound target
Depends: make, gcc | c-compiler, bzip2, debhelper (>= 4.0.0), module-assistant | kernel-package
Binary for arch all (17.3 KB) | dsc file | Source dir
(backport from 2.6.25 kernel tree)
Homepage: http://wiki.ltsp.org/twiki/bin/view/Ltsp/SoundCards
sis7019-source (1.0.0-2) - sis7019 driver for vortex sound target
Depends: make, gcc | c-compiler, bzip2, debhelper (>= 4.0.0), module-assistant | kernel-package
Binary for arch all (24.2 KB) | dsc file | Source dir
Homepage: http://wiki.ltsp.org/twiki/bin/view/Ltsp/SoundCards
EDIT: Also found this:http://git.kernel.org/git/?p=linux/kern ... 7072cc2b72
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
This one:
http://www.tcosproject.org/pool/main/s/ ... ty1.tar.gz
is probably the one you need.
As for mixing/matching kernel versions, remove the slackware kernel-sources package and then download, patch and configure the puppy kernel sources -place them in /usr/src with a link /usr/src/linux to the real directory. You'll still have to hack the driver Makefile to have it build the right sources, using the right headers... Still some room for you to learn more here , as I can't do it all for you at the moment.
edit:
On looking at it harder, maybe you just need to enable that module in the kernel configuration as it seems to already be part of the kernel.
end edit
As to your idea about kernel sources in an sfs, I used to have a small USB-based distro where I kept the kernel sources as an iso image which got mounted on /usr/src/linux. this will usually work -provided the sources are pre-configured as I outlined. And, of course, if you want to build them you have to do it from a separate dir:
mkdir /usr/src/my-kernel
cd /usr/src/my-kernel
'make -f ../linux/Makefile menuconfig'
then
'make bzImage' ,etc,etc
http://www.tcosproject.org/pool/main/s/ ... ty1.tar.gz
is probably the one you need.
As for mixing/matching kernel versions, remove the slackware kernel-sources package and then download, patch and configure the puppy kernel sources -place them in /usr/src with a link /usr/src/linux to the real directory. You'll still have to hack the driver Makefile to have it build the right sources, using the right headers... Still some room for you to learn more here , as I can't do it all for you at the moment.
edit:
On looking at it harder, maybe you just need to enable that module in the kernel configuration as it seems to already be part of the kernel.
end edit
As to your idea about kernel sources in an sfs, I used to have a small USB-based distro where I kept the kernel sources as an iso image which got mounted on /usr/src/linux. this will usually work -provided the sources are pre-configured as I outlined. And, of course, if you want to build them you have to do it from a separate dir:
mkdir /usr/src/my-kernel
cd /usr/src/my-kernel
'make -f ../linux/Makefile menuconfig'
then
'make bzImage' ,etc,etc
Here it is - first time I've got wifi working on the eBox-2300. Check out the attached screenshot.
Thanks Joe. This driver should be included in SlaxerPup.
Gotta go - after bedtime...
Thanks Joe. This driver should be included in SlaxerPup.
Gotta go - after bedtime...
- Attachments
-
- ebox2300-vt6655-3.png
- SlaxerPup running on eBox-2300 and connected via wlan (vt6655)
- (140.4 KiB) Downloaded 591 times
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Hey Paul (pakt)
EXCELLENT!
and just a reminder a big thanks for fixing the USB install
anything else for those mini systems let me know
love to see Slaxer_Pup on those
-------------------------------------
@Gilbert (amigo)
------------------------------------
if you need the slaxer kernel sources
here they are its a *.tgz because you wont have symlink problems
and it is all writeable and if you wanted to strip it down its easier to do
also it will install in the correct place and uninstall without any problems to your system
UPDATED 12-29-2009 lite version
src-kernel-slxr-2.6.27.7 Now 71MB 250 MB installed make sure you have the space first though
http://puppy2.org/slaxer/src-kernel-slx ... 2-slxr.tgz
if anyone compiles extra drivers let me know I will include them for slaxer pup
and upload them also
Thanks
Joe
Here it is - first time I've got wifi working on the eBox-2300. Check out the attached screenshot. Razz
EXCELLENT!
and just a reminder a big thanks for fixing the USB install
anything else for those mini systems let me know
love to see Slaxer_Pup on those
-------------------------------------
@Gilbert (amigo)
Thanks Gilbert I was going to check that out todayAbout the sound card driver, if you are using kernel >= 2.6.25 the driver is already in the kernel sources. The sources you linked to are for backporting the driver to earlier kernel versions.
------------------------------------
if you need the slaxer kernel sources
here they are its a *.tgz because you wont have symlink problems
and it is all writeable and if you wanted to strip it down its easier to do
also it will install in the correct place and uninstall without any problems to your system
UPDATED 12-29-2009 lite version
src-kernel-slxr-2.6.27.7 Now 71MB 250 MB installed make sure you have the space first though
http://puppy2.org/slaxer/src-kernel-slx ... 2-slxr.tgz
if anyone compiles extra drivers let me know I will include them for slaxer pup
and upload them also
Thanks
Joe
Last edited by big_bass on Tue 29 Dec 2009, 18:58, edited 1 time in total.
Joe, I think you must be distributing the kernel sources with all the objects built which, if so, is unnecessary. The unpacked sources should be in the range of 200-250MB.
for them to be fully functional, they only need to be configured and then packed up:
'make clean oldconfig prepare'
That will make them usable for compiling out-of-tree sources and also make them available for re-compiling the kernel or any in-tree modules in the exact form in which you used them to produce your kernel and modules.
Packing them should give you a tgz package in the range of ~80MB or so, and if your use txz then probably about 65MB.
You might have a look at delivering them as an iso image as I metioned before -that will keep them to 65/80MB installed. the only caveat is that you can't build directly in the (read-only) tree. You could create a zisofs image (using mkzftree) to keep the gzip compression. Then deliver it installed as:
/usr/src/linux/.linux-sources.iso
Then you could have the packages' doinst.sh create an entry in /etc/rc.d/rc.local which would loop-mount the image -something like this:
You could use losetup, but if you are using loop devices you'd need to do a losetup -f to find a free device first. This method shows how to 'overmount' a directory with the contents of the directory in such a way that the original content (the *.iso) is invisible.
Since you are probably more comfortable with sfs files/mounts, you could do it that way. I worked out the above trick long ago -one of the priorities was to be able to use an unpatched kernel, and at the time squashfs was not a part of the kernel, so that's why zisofs was used.
Anyway, even if you don't do that, you can still deliver read-write sources at under 100MB *unpacked*.
for them to be fully functional, they only need to be configured and then packed up:
'make clean oldconfig prepare'
That will make them usable for compiling out-of-tree sources and also make them available for re-compiling the kernel or any in-tree modules in the exact form in which you used them to produce your kernel and modules.
Packing them should give you a tgz package in the range of ~80MB or so, and if your use txz then probably about 65MB.
You might have a look at delivering them as an iso image as I metioned before -that will keep them to 65/80MB installed. the only caveat is that you can't build directly in the (read-only) tree. You could create a zisofs image (using mkzftree) to keep the gzip compression. Then deliver it installed as:
/usr/src/linux/.linux-sources.iso
Then you could have the packages' doinst.sh create an entry in /etc/rc.d/rc.local which would loop-mount the image -something like this:
Code: Select all
if [[ -f /usr/src/linux/.linux-sources.iso ]] ; then
# losetup /dev/loop-whatever /usr/src/linux/.linux-sources.iso
# mount /dev/loop-whatever /usr/src/linux
mount -o loop -t iso9660 /usr/src/linux/.linux-sources.iso /usr/src/linux
fi
Since you are probably more comfortable with sfs files/mounts, you could do it that way. I worked out the above trick long ago -one of the priorities was to be able to use an unpatched kernel, and at the time squashfs was not a part of the kernel, so that's why zisofs was used.
Anyway, even if you don't do that, you can still deliver read-write sources at under 100MB *unpacked*.
Thanks for the pointers on changing kernels in Slackware, Gilbert. I'll put that on the backburner for now and concentrate on using the kernel headers with SlaxerPupStill some room for you to learn more here , as I can't do it all for you at the moment.
I downloaded the kernel source for SlaxerPup (Thanks Joe ) and checked the contents. If I'm not mistaken these branches can be removed:
- All branches off arch/ except for /x86, i.e. remove branches alpha, arm, avr32, blackfin, cris, frv, h8300, ia64, m32r, m68k, mips, mn10300, parisc, powerpc, s390, sh, sparc, um and xtensa.
- The /Documentation branch
- All .o* files (includes .o.cmd, .o.uu, etc files. I assume these are all object files)
I'm just familiar with a few tar commands. Any tips on the tar command options to (easily) remove the above branches from the compressed tarball
Last question: I found sis7019.c and sis7019.h in the source. How would I compile just the sis7019 module and not the rest of the source?
Paul
Methinks Raspberry Pi were ideal for runnin' Puppy Linux