Message-
From: Antoine Delvaux [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 15, 2002 4:23 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; debian-powerpc@lists.debian.org
Subject: RE: eata.c module and PCI setup problem (RAID SCSI card)
Hello all,
Thank you for your
Hello all,
Thank you for your feedback and sorry for being late. I was the whole
week in a Juniper training in Holland and had not been able to test this
new driver. I just done it today.
Here is the syslog output I've got when doing 'insmod eata.o' or 'insmod
eata.o io_port=0x1410' :
Jun 15
On Sun, 9 Jun 2002, Michel Lanners wrote:
On 9 Jun, this message from [EMAIL PROTECTED] echoed through cyberspace:
With this value both the auto detection and the io_port option
would give the same (good) behavior.
The real problem is that the driver expects the EATA signature
(big
vale niente lui.
---
From: Geert Uytterhoeven [mailto:[EMAIL PROTECTED]
Sent: Monday, June 10, 2002 9:53 AM
To: Michel Lanners
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Debian GNU/Linux PPC
Subject: Re: eata.c module and PCI setup problem (RAID SCSI card)
On Sun, 9 Jun 2002, Michel Lanners wrote
On Mon, 10 Jun 2002 [EMAIL PROTECTED] wrote:
Unfortunately the EATA PIO protocol just works for 16 bits transfers,
so inw is the only option.
le16_to_cpu(inw()) should give the expected result for both BE and LE.
Since the detection routine checks for both EATA and ATAE signatures,
all
/06/02 8.20
Subject: Re: eata.c module and PCI setup problem (RAID SCSI card)
Hello Michel and Ballabio,
I've integrated the few debug changes from Michel and new Ballabio's
code. Here are a few answers and description of what is happening now.
But I want to already thank you for your
. Let's see if the driver works first.
-db
-Original Message-
From: Michel Lanners
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; debian-powerpc@lists.debian.org
Sent: 09/06/02 17.16
Subject: Re: eata.c module and PCI setup problem (RAID SCSI card)
Hi Ballabio,
On 9 Jun, this message from
-powerpc@lists.debian.org
Subject: Re: eata.c module and PCI setup problem (RAID SCSI card)
Hi,
On 6 Jun, this message from [EMAIL PROTECTED] echoed through
cyberspace:
The eata driver really does not care whether it is using an ISA, EISA or
PCI
board
It should, though. On most (all?) platforms
On 6 Jun, this message from Antoine Delvaux echoed through cyberspace:
in the module source. That doesn't output much though...
Jun 5 09:23:22 brocoli kernel: IN from bad port 338 at d006092c
Jun 5 09:23:22 brocoli kernel: IN from bad port 338 at d006092c
Jun 5 09:23:22 brocoli
valgono niente o non vale niente lui.
-Original Message-
From: Michel Lanners [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 06, 2002 8:09 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; debian-powerpc@lists.debian.org
Subject: Re: eata.c module and PCI setup problem (RAID SCSI card
Hi,
On 6 Jun, this message from [EMAIL PROTECTED] echoed through cyberspace:
The eata driver really does not care whether it is using an ISA, EISA or PCI
board
It should, though. On most (all?) platforms besides i386, there are huge
differences between ISA/EISA and PCI. You can't just assume
On 4 Jun, this message from Antoine Delvaux echoed through cyberspace:
I'm currently trying to make a DPT PM2144UW PCI card with a
SmartCache IV and 64 MB working. It's a UW SCSI raid controller. The
card is working fine in an Intel based box with the eata driver. But in
my PowerMac 7500
Le mercredi 5 juin 2002 vers 8:19, Michel Lanners écrivait :
On 4 Jun, this message from Antoine Delvaux echoed through
cyberspace:
Since two days I've been in touch with the developper of the eata.c
driver (Ballabio Dario) and he gave me a few debug version of that
driver to play with.
On Wed, 5 Jun 2002, Antoine Delvaux wrote:
Le mercredi 5 juin 2002 vers 8:19, Michel Lanners écrivait :
On 4 Jun, this message from Antoine Delvaux echoed through
cyberspace:
Since two days I've been in touch with the developper of the eata.c
driver (Ballabio Dario) and he gave me a few
# insmod eata.o io_port=0x1400
^^
Where are you getting this value from? I'm sure it is wrong... Have
a look at the boot messages of your kernel, and also send along the
output of 'lspci -vv'.
I'm getting this addresse from lspci and from previous tries
On Wed, 5 Jun 2002, Antoine Delvaux wrote:
# insmod eata.o io_port=0x1400
^^
Where are you getting this value from? I'm sure it is wrong... Have
a look at the boot messages of your kernel, and also send along the
output of 'lspci -vv'.
I'm
On 5 Jun, this message from Antoine Delvaux echoed through cyberspace:
Le mercredi 5 juin 2002 vers 8:19, Michel Lanners écrivait :
# insmod eata.o io_port=0x1400
^^
Where are you getting this value from?
I'm getting this addresse from lspci and from previous
in the module source. That doesn't output much though...
Jun 5 09:23:22 brocoli kernel: IN from bad port 338 at d006092c
Jun 5 09:23:22 brocoli kernel: IN from bad port 338 at d006092c
Jun 5 09:23:22 brocoli last message repeated 452 times
Jun 5 09:23:22 brocoli kernel: EATA0:
18 matches
Mail list logo
