Daniela,
Great to hear from you again my dear! ;-)
On Fri, 9 Mar 2001, Vojtech Pavlik wrote:
> On Fri, Mar 09, 2001 at 08:25:43AM +0100, Daniela Engert wrote:
>
> > >They're about the same - only Alan didn't like the PCI speed measurement
> > >code that's new in the 4.x series, so I added
Daniela,
Great to hear from you again my dear! ;-)
On Fri, 9 Mar 2001, Vojtech Pavlik wrote:
On Fri, Mar 09, 2001 at 08:25:43AM +0100, Daniela Engert wrote:
They're about the same - only Alan didn't like the PCI speed measurement
code that's new in the 4.x series, so I added all the
On Fri, Mar 09, 2001 at 09:10:32PM -0500, David Huggins-Daines wrote:
> It's the one listed in arch/i386/defconfig. Of course, it's debatable
> whether that actually means 'default' or not (since in fact it's more
> like 'what Linus uses'), but plenty of people will see it as such.
Thanks for
On Fri, Mar 09, 2001 at 09:10:32PM -0500, David Huggins-Daines wrote:
It's the one listed in arch/i386/defconfig. Of course, it's debatable
whether that actually means 'default' or not (since in fact it's more
like 'what Linus uses'), but plenty of people will see it as such.
Thanks for
Greg KH <[EMAIL PROTECTED]> writes:
> On Fri, Mar 09, 2001 at 02:13:32PM -0600, Erik DeBill wrote:
> > Until it's documented this is a landmine. JE is the default USB
> > driver, so you can bet that a great many people will be using it (even
> > though it's described as "alternate"). Once it's
On Fri, Mar 09, 2001 at 02:13:32PM -0600, Erik DeBill wrote:
> Nothing. I've got the following in /etc/syslog.conf (which I believe
> SHOULD be correct), but I get absolutely nothing.
>
> *.=debug;\
> auth,authpriv.none;\
> news.none;mail.none /var/log/debug
Try adding an entry
On Thu, Mar 08, 2001 at 04:07:58PM -0800, Greg KH wrote:
> > Hmm... I was compiling usb-uhci and uhci directly into the kernel,
> > then visor.o as a module.
>
> You shouldn't be able to compile both usb-uhci and uhci into the kernel,
> unless you tweak your .config file by hand.
Build 2
On Fri, Mar 09, 2001 at 06:10:56AM -0700, Harold Oga wrote:
>On Thu, Mar 08, 2001 at 09:54:48PM +0100, Vojtech Pavlik wrote:
>>3.21 has these fixes in it. It's series 3 because it doesn't include the
>>PCI speed measurement feature.
>Hi,
> Hmm, ok, I'll have to go back and try it again, because
On Thu, Mar 08, 2001 at 09:54:48PM +0100, Vojtech Pavlik wrote:
>On Thu, Mar 08, 2001 at 11:35:42AM -0700, Harold Oga wrote:
>
>> On Thu, Mar 08, 2001 at 09:17:06AM +0100, Vojtech Pavlik wrote:
>> >On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
>> >Make sure you use the latest
On Thu, Mar 08, 2001 at 09:54:48PM +0100, Vojtech Pavlik wrote:
On Thu, Mar 08, 2001 at 11:35:42AM -0700, Harold Oga wrote:
On Thu, Mar 08, 2001 at 09:17:06AM +0100, Vojtech Pavlik wrote:
On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
Make sure you use the latest 2.4.2-acxx
On Fri, Mar 09, 2001 at 06:10:56AM -0700, Harold Oga wrote:
On Thu, Mar 08, 2001 at 09:54:48PM +0100, Vojtech Pavlik wrote:
3.21 has these fixes in it. It's series 3 because it doesn't include the
PCI speed measurement feature.
Hi,
Hmm, ok, I'll have to go back and try it again, because I
On Thu, Mar 08, 2001 at 04:07:58PM -0800, Greg KH wrote:
Hmm... I was compiling usb-uhci and uhci directly into the kernel,
then visor.o as a module.
You shouldn't be able to compile both usb-uhci and uhci into the kernel,
unless you tweak your .config file by hand.
Build 2 kernels,
On Fri, Mar 09, 2001 at 02:13:32PM -0600, Erik DeBill wrote:
Nothing. I've got the following in /etc/syslog.conf (which I believe
SHOULD be correct), but I get absolutely nothing.
*.=debug;\
auth,authpriv.none;\
news.none;mail.none /var/log/debug
Try adding an entry for
Greg KH [EMAIL PROTECTED] writes:
On Fri, Mar 09, 2001 at 02:13:32PM -0600, Erik DeBill wrote:
Until it's documented this is a landmine. JE is the default USB
driver, so you can bet that a great many people will be using it (even
though it's described as "alternate"). Once it's fixed we
On Fri, Mar 09, 2001 at 08:25:43AM +0100, Daniela Engert wrote:
> >They're about the same - only Alan didn't like the PCI speed measurement
> >code that's new in the 4.x series, so I added all the other changes to
> >the 3.20 driver, and 3.21 was born.
>
> I do understand Alan's objections
On Thu, 8 Mar 2001 19:51:07 +0100, Vojtech Pavlik wrote:
>They're about the same - only Alan didn't like the PCI speed measurement
>code that's new in the 4.x series, so I added all the other changes to
>the 3.20 driver, and 3.21 was born.
I do understand Alan's objections against this speed
On Thu, Mar 08, 2001 at 11:35:42AM -0700, Harold Oga wrote:
> On Thu, Mar 08, 2001 at 09:17:06AM +0100, Vojtech Pavlik wrote:
> >On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
> >Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
> >my drivers have little bugs in
On Thu, Mar 08, 2001 at 02:01:03PM -0600, Erik DeBill wrote:
> On Wed, Mar 07, 2001 at 05:36:40PM -0800, Greg KH wrote:
> > I'll try to run with everything compiled into the kernel later tonight.
> > Does -ac14 with all of USB as modules, using usb-uhci work for you?
>
> Hmm... I was compiling
On Wed, Mar 07, 2001 at 05:36:40PM -0800, Greg KH wrote:
> I'll try to run with everything compiled into the kernel later tonight.
> Does -ac14 with all of USB as modules, using usb-uhci work for you?
Hmm... I was compiling usb-uhci and uhci directly into the kernel,
then visor.o as a module.
On Thu, Mar 08, 2001 at 09:30:23AM -0800, Wayne Whitney wrote:
> In mailing-lists.linux-kernel, you wrote:
>
> > Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
> > my drivers have little bugs in the 686b support. Harmless but somewhat
> > annoying.
>
> Does this mean
On Thu, Mar 08, 2001 at 09:17:06AM +0100, Vojtech Pavlik wrote:
>On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
>Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
>my drivers have little bugs in the 686b support. Harmless but somewhat
>annoying.
Hi,
Hmm, last
In mailing-lists.linux-kernel, you wrote:
> Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
> my drivers have little bugs in the 686b support. Harmless but somewhat
> annoying.
Does this mean that the version 3.21 of your driver in the latest
2.4.2-acxx is newer than the
On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
> > Also, the vt82c686 will work just fine with Linux, but will be limited
> > to UDMA33, because UDMA66 on this chip does reliably fail.
>
> Based on following the lkml threads on Via chipsets, it seems that
> the 686a at or above rev
On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
Also, the vt82c686 will work just fine with Linux, but will be limited
to UDMA33, because UDMA66 on this chip does reliably fail.
Based on following the lkml threads on Via chipsets, it seems that
the 686a at or above rev 22,
In mailing-lists.linux-kernel, you wrote:
Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
my drivers have little bugs in the 686b support. Harmless but somewhat
annoying.
Does this mean that the version 3.21 of your driver in the latest
2.4.2-acxx is newer than the
On Thu, Mar 08, 2001 at 09:17:06AM +0100, Vojtech Pavlik wrote:
On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
my drivers have little bugs in the 686b support. Harmless but somewhat
annoying.
Hi,
Hmm, last I
On Thu, Mar 08, 2001 at 09:30:23AM -0800, Wayne Whitney wrote:
In mailing-lists.linux-kernel, you wrote:
Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
my drivers have little bugs in the 686b support. Harmless but somewhat
annoying.
Does this mean that the
On Wed, Mar 07, 2001 at 05:36:40PM -0800, Greg KH wrote:
I'll try to run with everything compiled into the kernel later tonight.
Does -ac14 with all of USB as modules, using usb-uhci work for you?
Hmm... I was compiling usb-uhci and uhci directly into the kernel,
then visor.o as a module.
In
On Thu, Mar 08, 2001 at 02:01:03PM -0600, Erik DeBill wrote:
On Wed, Mar 07, 2001 at 05:36:40PM -0800, Greg KH wrote:
I'll try to run with everything compiled into the kernel later tonight.
Does -ac14 with all of USB as modules, using usb-uhci work for you?
Hmm... I was compiling usb-uhci
On Thu, 8 Mar 2001 19:51:07 +0100, Vojtech Pavlik wrote:
They're about the same - only Alan didn't like the PCI speed measurement
code that's new in the 4.x series, so I added all the other changes to
the 3.20 driver, and 3.21 was born.
I do understand Alan's objections against this speed
On Thu, Mar 08, 2001 at 11:35:42AM -0700, Harold Oga wrote:
On Thu, Mar 08, 2001 at 09:17:06AM +0100, Vojtech Pavlik wrote:
On Wed, Mar 07, 2001 at 01:23:49PM +, John Heil wrote:
Make sure you use the latest 2.4.2-acxx drivers. Most other versions of
my drivers have little bugs in the
On Fri, Mar 09, 2001 at 08:25:43AM +0100, Daniela Engert wrote:
They're about the same - only Alan didn't like the PCI speed measurement
code that's new in the 4.x series, so I added all the other changes to
the 3.20 driver, and 3.21 was born.
I do understand Alan's objections against this
On Mar 07 2001, Vojtech Pavlik wrote:
> Also, the vt82c686 will work just fine with Linux, but will be limited
> to UDMA33, because UDMA66 on this chip does reliably fail.
How do I know which one I have? Using the revision of the
chip?
lspci only shows that I have a
On Wed, Mar 07, 2001 at 05:20:56PM -0600, Erik DeBill wrote:
>
> I went to install some new software on my Visor yesterday and got a
> rude surpise, as my system froze hard (unpingable, no response to
> keyboard or mouse, no oops). A bit of experimenting shows:
>
> It works fine with usb-uhci
I've been running with just that single visor patch on 2.4.2 for quite
some time now. But I'm building ac13 right now, and I'll let you know
what I find out in a bit.
thanks for letting me know.
greg k-h
--
greg@(kroah|wirex).com
-
To unsubscribe from this list: send the line "unsubscribe
> On ac12 and 13 if the visor driver is compiled into the kernel it wil=
> l
> work poorly for a time (very slow sync, jpilot/pilot-link complains o=
Does 2.4.2ac11 work - I ask this as ac12 has some visro changes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
I went to install some new software on my Visor yesterday and got a
rude surpise, as my system froze hard (unpingable, no response to
keyboard or mouse, no oops). A bit of experimenting shows:
It works fine with usb-uhci in all versions I tested.
Plain 2.4.2 works fine with either usb-uhci or
On Wed, 7 Mar 2001, Vojtech Pavlik wrote:
> Date: Wed, 7 Mar 2001 20:14:37 +0100
> From: Vojtech Pavlik <[EMAIL PROTECTED]>
> To: George Garvey <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: Linux 2.4.2ac12 (vt82c686 info)
>
> On Tue, Mar 06, 2001 a
On Tue, Mar 06, 2001 at 05:05:46AM -0800, George Garvey wrote:
>
> > No, just the vt82c686. vt82c686a and vt82c686b are OK.
>
> So can the vt82c686 be replaced with one of these other chips? What
> action is available to owners of MBs with chips that don't work w/Linux?
It can be replaced if
On Tue, Mar 06, 2001 at 05:05:46AM -0800, George Garvey wrote:
No, just the vt82c686. vt82c686a and vt82c686b are OK.
So can the vt82c686 be replaced with one of these other chips? What
action is available to owners of MBs with chips that don't work w/Linux?
It can be replaced if you can
I went to install some new software on my Visor yesterday and got a
rude surpise, as my system froze hard (unpingable, no response to
keyboard or mouse, no oops). A bit of experimenting shows:
It works fine with usb-uhci in all versions I tested.
Plain 2.4.2 works fine with either usb-uhci or
On ac12 and 13 if the visor driver is compiled into the kernel it wil=
l
work poorly for a time (very slow sync, jpilot/pilot-link complains o=
Does 2.4.2ac11 work - I ask this as ac12 has some visro changes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Wed, Mar 07, 2001 at 05:20:56PM -0600, Erik DeBill wrote:
I went to install some new software on my Visor yesterday and got a
rude surpise, as my system froze hard (unpingable, no response to
keyboard or mouse, no oops). A bit of experimenting shows:
It works fine with usb-uhci in all
On Mar 07 2001, Vojtech Pavlik wrote:
Also, the vt82c686 will work just fine with Linux, but will be limited
to UDMA33, because UDMA66 on this chip does reliably fail.
How do I know which one I have? Using the revision of the
chip?
lspci only shows that I have a
> No, just the vt82c686. vt82c686a and vt82c686b are OK.
So can the vt82c686 be replaced with one of these other chips? What
action is available to owners of MBs with chips that don't work w/Linux?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.2-ac12
o Move the pci_enable_device for cardbus (David Hinds)
o Add Sony MSC-U01N to the unusual devices(Marcel
Holtmann)
o Final smc-mca fixups - should now work (James
Bottomley)
o
On Mon, Mar 05, 2001 at 04:37:00PM -0500, David Riley wrote:
> Alan Cox wrote:
> > 2.4.2-ac12
> > o Update VIA IDE driver to 3.21 (Vojtech Pavlik)
> > |No UDMA66 on 82c686
>
> Um... Does that include 686a? 82c686a is supposed to handle UDMA66...
> Or is it a
On Mon, Mar 05, 2001 at 04:37:00PM -0500, David Riley wrote:
Alan Cox wrote:
2.4.2-ac12
o Update VIA IDE driver to 3.21 (Vojtech Pavlik)
|No UDMA66 on 82c686
Um... Does that include 686a? 82c686a is supposed to handle UDMA66...
Or is it a corruption
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.2-ac12
o Move the pci_enable_device for cardbus (David Hinds)
o Add Sony MSC-U01N to the unusual devices(Marcel
Holtmann)
o Final smc-mca fixups - should now work (James
Bottomley)
o
No, just the vt82c686. vt82c686a and vt82c686b are OK.
So can the vt82c686 be replaced with one of these other chips? What
action is available to owners of MBs with chips that don't work w/Linux?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Tue, 6 Mar 2001, Alan Cox wrote:
> > Yuck. Build-dependency on libdb-dev is not pretty. What is it used for,
> > anyway? Assembler in need of libdb. Mind boggleth...
>
> Could it perhaps be persuaded to use Tridge's tdb, which at < 1000 lines could
> simply be included with it...
Alan,
> May be. But it's not a reason to use the _OBSOLETE_ library. At least the
> current one should be used...
>
> Here comes the patch to use current libdb-3...
Not all vendors ship db3. I'm not sure its a stunning improvement, but its
the right first step. Will apply
-
To unsubscribe from this
for the aic7xxx risc instruction code, not part
> of
> the driver
May be. But it's not a reason to use the _OBSOLETE_ library. At least the
current one should be used...
Here comes the patch to use current libdb-3...
=== Cut ===
diff -urN linux-2.4.2ac12.orig/drivers/scsi/aic7xxx/aicasm
> Yuck. Build-dependency on libdb-dev is not pretty. What is it used for,
> anyway? Assembler in need of libdb. Mind boggleth...
Could it perhaps be persuaded to use Tridge's tdb, which at < 1000 lines could
simply be included with it...
-
To unsubscribe from this list: send the line
> On Mon, 5 Mar 2001, Alexander Viro wrote:
>
> New Adaptec driver does not build. It won't. People, can anyone enlighten me
> why do we use a user space library for a kernel driver at all?
aicasm is an assembler for the aic7xxx risc instruction code, not part of
the driver
-
To unsubscribe
Sergey Kubushin wrote:
> I _DO_ know what db1 stands for. And we do _NOT_ have db1 in our
> distribution, KSI Linux. And we are _NOT_ going to build the obsolete
> library with all the accompanied development stuff just to be able to make
> some tool required to build exactly ONE kernel driver.
On 03.06 Sergey Kubushin wrote:
> On Mon, 5 Mar 2001, J . A . Magallon wrote:
>
> > What that line does is to build a tool (aicasm) to generate the ucode
> > that
> > is built into the kernel (afaik, it is a kind of assembler from a
> > language
> > to AIC sequencer code). That is, the tool
On Mon, 5 Mar 2001, Jeff Garzik wrote:
> Amazingly you've hit one of the few problems caused by something
> outside
> the kernel tree. db v1.85 has been superceded by db2 and db3. db1 is
> where the "original" Berkeley db stuff now lives. Apparently aicasm
> needs db 1.
>
> So, update your
On Mon, 5 Mar 2001, J . A . Magallon wrote:
> What that line does is to build a tool (aicasm) to generate the ucode
> that
> is built into the kernel (afaik, it is a kind of assembler from a
> language
> to AIC sequencer code). That is, the tool uses db1 (as mkdep.c uses
> glibc)
> but once you
On Mon, 5 Mar 2001, J . A . Magallon wrote:
>
> On 03.05 Sergey Kubushin wrote:
> > On Mon, 5 Mar 2001, Alexander Viro wrote:
> >
> > New Adaptec driver does not build. It won't. People, can anyone enlighten me
> > why do we use a user space library for a kernel driver at all?
> >
> > gcc
Sergey Kubushin wrote:
> === Cut ===
> make -C aic7xxx modules
> make[3]: Entering directory
>`/tmp/build-kernel/usr/src/linux-2.4.2ac12/drivers/scsi/aic7xxx'
> make -C aicasm
> make[4]: Entering directory
>`/tmp/build-kernel/usr/src/linux-2.4.2ac12/drivers/scsi/aic7xxx
On 03.05 Sergey Kubushin wrote:
> On Mon, 5 Mar 2001, Alexander Viro wrote:
>
> New Adaptec driver does not build. It won't. People, can anyone enlighten me
> why do we use a user space library for a kernel driver at all?
>
> gcc -I/usr/include -ldb1 aicasm_gram.c aicasm_scan.c aicasm.c
On Mon, 5 Mar 2001, Alexander Viro wrote:
New Adaptec driver does not build. It won't. People, can anyone enlighten me
why do we use a user space library for a kernel driver at all?
=== Cut ===
make -C aic7xxx modules
make[3]: Entering directory
`/tmp/build-kernel/usr/src/linux-2.4.2ac12
It appears that with 2.4.2-ac12, we now have more than 2000
kernel configuration options.
Using the options_linux script which I posted earlier today,
I get the following:
[steven@spc linux]$ sh scripts/options_linux | wc -l
2008
Compare to 2.2.18:
[root@spc linux-2.2.18]# sh
I've used 82c686a at UDMA66 on MSI 694D with WD418000 and standard UDMA66 18"
cables quite successfully.
David Riley wrote:
> Alan Cox wrote:
> > 2.4.2-ac12
> > o Update VIA IDE driver to 3.21 (Vojtech Pavlik)
> > |No UDMA66 on 82c686
>
> Um... Does that include
Alan Cox wrote:
> 2.4.2-ac12
> o Update VIA IDE driver to 3.21 (Vojtech Pavlik)
> |No UDMA66 on 82c686
Um... Does that include 686a? 82c686a is supposed to handle UDMA66...
Or is it a corruption issue again? UDMA66 seems to work fine on
mine... No corruptions
On Mon, 5 Mar 2001, Alan Cox wrote:
> o Fix binfmt_misc (and make the proc handling (Al Viro)
> |a filesystem -
> |mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
One comment: probably the best way to maintain backwards compatibility
for people who used binfmt_misc as a
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.2-ac12
o Move the pci_enable_device for cardbus (David Hinds)
o Add Sony MSC-U01N to the unusual devices(Marcel Holtmann)
o Final smc-mca fixups - should now work (James Bottomley)
o
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.2-ac12
o Move the pci_enable_device for cardbus (David Hinds)
o Add Sony MSC-U01N to the unusual devices(Marcel Holtmann)
o Final smc-mca fixups - should now work (James Bottomley)
o
On Mon, 5 Mar 2001, Alan Cox wrote:
o Fix binfmt_misc (and make the proc handling (Al Viro)
|a filesystem -
|mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
One comment: probably the best way to maintain backwards compatibility
for people who used binfmt_misc as a
Alan Cox wrote:
2.4.2-ac12
o Update VIA IDE driver to 3.21 (Vojtech Pavlik)
|No UDMA66 on 82c686
Um... Does that include 686a? 82c686a is supposed to handle UDMA66...
Or is it a corruption issue again? UDMA66 seems to work fine on
mine... No corruptions yet.
I've used 82c686a at UDMA66 on MSI 694D with WD418000 and standard UDMA66 18"
cables quite successfully.
David Riley wrote:
Alan Cox wrote:
2.4.2-ac12
o Update VIA IDE driver to 3.21 (Vojtech Pavlik)
|No UDMA66 on 82c686
Um... Does that include 686a?
It appears that with 2.4.2-ac12, we now have more than 2000
kernel configuration options.
Using the options_linux script which I posted earlier today,
I get the following:
[steven@spc linux]$ sh scripts/options_linux | wc -l
2008
Compare to 2.2.18:
[root@spc linux-2.2.18]# sh
On Mon, 5 Mar 2001, Alexander Viro wrote:
New Adaptec driver does not build. It won't. People, can anyone enlighten me
why do we use a user space library for a kernel driver at all?
=== Cut ===
make -C aic7xxx modules
make[3]: Entering directory
`/tmp/build-kernel/usr/src/linux-2.4.2ac12
On 03.05 Sergey Kubushin wrote:
On Mon, 5 Mar 2001, Alexander Viro wrote:
New Adaptec driver does not build. It won't. People, can anyone enlighten me
why do we use a user space library for a kernel driver at all?
gcc -I/usr/include -ldb1 aicasm_gram.c aicasm_scan.c aicasm.c
Sergey Kubushin wrote:
=== Cut ===
make -C aic7xxx modules
make[3]: Entering directory
`/tmp/build-kernel/usr/src/linux-2.4.2ac12/drivers/scsi/aic7xxx'
make -C aicasm
make[4]: Entering directory
`/tmp/build-kernel/usr/src/linux-2.4.2ac12/drivers/scsi/aic7xxx/aicasm'
gcc -I/usr/include
On Mon, 5 Mar 2001, J . A . Magallon wrote:
On 03.05 Sergey Kubushin wrote:
On Mon, 5 Mar 2001, Alexander Viro wrote:
New Adaptec driver does not build. It won't. People, can anyone enlighten me
why do we use a user space library for a kernel driver at all?
gcc -I/usr/include
On Mon, 5 Mar 2001, J . A . Magallon wrote:
What that line does is to build a tool (aicasm) to generate the ucode
that
is built into the kernel (afaik, it is a kind of assembler from a
language
to AIC sequencer code). That is, the tool uses db1 (as mkdep.c uses
glibc)
but once you have
On Mon, 5 Mar 2001, Jeff Garzik wrote:
Amazingly you've hit one of the few problems caused by something
outside
the kernel tree. db v1.85 has been superceded by db2 and db3. db1 is
where the "original" Berkeley db stuff now lives. Apparently aicasm
needs db 1.
So, update your packages,
On 03.06 Sergey Kubushin wrote:
On Mon, 5 Mar 2001, J . A . Magallon wrote:
What that line does is to build a tool (aicasm) to generate the ucode
that
is built into the kernel (afaik, it is a kind of assembler from a
language
to AIC sequencer code). That is, the tool uses db1 (as
Sergey Kubushin wrote:
I _DO_ know what db1 stands for. And we do _NOT_ have db1 in our
distribution, KSI Linux. And we are _NOT_ going to build the obsolete
library with all the accompanied development stuff just to be able to make
some tool required to build exactly ONE kernel driver. It
On Mon, 5 Mar 2001, Alexander Viro wrote:
New Adaptec driver does not build. It won't. People, can anyone enlighten me
why do we use a user space library for a kernel driver at all?
aicasm is an assembler for the aic7xxx risc instruction code, not part of
the driver
-
To unsubscribe from
Yuck. Build-dependency on libdb-dev is not pretty. What is it used for,
anyway? Assembler in need of libdb. Mind boggleth...
Could it perhaps be persuaded to use Tridge's tdb, which at 1000 lines could
simply be included with it...
-
To unsubscribe from this list: send the line "unsubscribe
, not part
of
the driver
May be. But it's not a reason to use the _OBSOLETE_ library. At least the
current one should be used...
Here comes the patch to use current libdb-3...
=== Cut ===
diff -urN linux-2.4.2ac12.orig/drivers/scsi/aic7xxx/aicasm/Makefile
linux-2.4.2ac12/drivers/scsi/aic7xxx/aicasm
On Tue, 6 Mar 2001, Alan Cox wrote:
Yuck. Build-dependency on libdb-dev is not pretty. What is it used for,
anyway? Assembler in need of libdb. Mind boggleth...
Could it perhaps be persuaded to use Tridge's tdb, which at 1000 lines could
simply be included with it...
Alan, AFAICS
85 matches
Mail list logo
