[parisc-linux] FC driver?

[parisc-linux] FC driver?

[Joel Soete]

Hi all,

On the N4000 which I can test for a short time there are fc cards.
lspci give me following info about those cards:

20:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host
Adapter (rev 0b)
d0:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host
Adapter (rev 0b)
e0:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host
Adapter (rev 0b)

The question is: which driver should I use (cpqfc?)?

Thanks for info,
        Joel


---------------------------------
Vous surfez avec une ligne classique ?
Economisez jusqu'à 25% avec Tiscali Complete !
Offre spéciale : première année d'abonnement offerte.
... Plus d'info sur http://complete.tiscali.be

Re: [parisc-linux] FC driver?

[Jan-Benedict Glaw]

[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]

On Mon, 2003-03-17 12:05:20 +0100, Joel Soete <jsoe0708@tiscali.be>
wrote in message <3E68A12A00002910@ocpmta3.freegates.net>:
> Hi all,
> 
> On the N4000 which I can test for a short time there are fc cards.
> lspci give me following info about those cards:
> 
> 20:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host Adapter (rev 0b)
> d0:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host Adapter (rev 0b)
> e0:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host Adapter (rev 0b)

[line break-ups corrected]

> The question is: which driver should I use (cpqfc?)?

I do not have such a card, but:

/usr/share/misc/pci.ids:
103c  Hewlett-Packard Company
	1028  Tach TL Fibre Channel Host Adapter

So it seems your device is 103c:1028. In the kernel, this maps through
./linux/include/linux/pci_ids.h:

#define PCI_DEVICE_ID_HP_TACHYON      0x1028

So your device is called "PCI_DEVICE_ID_HP_TACHYON". Searching for this
string, you'll find it in ./linux/drivers/scsi/cpqfcTSinit.c, so that
card seems to be supported.

See, it's quite easy to see if a PCI card seems to be supported:-)

MfG, JBG



-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [parisc-linux] FC driver?

[Joel Soete]

>-- Original Message --
>From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
>To: parisc-linux@lists.parisc-linux.org
>Subject: Re: [parisc-linux] FC driver?
>Date: Mon, 17 Mar 2003 12:18:01 +0100
>
>
>On Mon, 2003-03-17 12:05:20 +0100, Joel Soete <jsoe0708@tiscali.be>
>wrote in message <3E68A12A00002910@ocpmta3.freegates.net>:
>> Hi all,
>> 
>> On the N4000 which I can test for a short time there are fc cards.
>> lspci give me following info about those cards:
>> 
>> 20:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host
>Adapter (rev 0b)
>> d0:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host
>Adapter (rev 0b)
>> e0:00.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel Host
>Adapter (rev 0b)
>
>[line break-ups corrected]
>
>> The question is: which driver should I use (cpqfc?)?
>
>I do not have such a card, but:
>
>/usr/share/misc/pci.ids:
>103c  Hewlett-Packard Company
>	1028  Tach TL Fibre Channel Host Adapter
>
>So it seems your device is 103c:1028. In the kernel, this maps through
>./linux/include/linux/pci_ids.h:
>
>#define PCI_DEVICE_ID_HP_TACHYON      0x1028
>
>So your device is called "PCI_DEVICE_ID_HP_TACHYON". Searching for this
>string, you'll find it in ./linux/drivers/scsi/cpqfcTSinit.c, so that
>card seems to be supported.
>
>See, it's quite easy to see if a PCI card seems to be supported:-)
>
>MfG, JBG
>
cool :)

Thanks a lot for those kind explanations,
    Joel


---------------------------------
Vous surfez avec une ligne classique ?
Economisez jusqu'à 25% avec Tiscali Complete !
Offre spéciale : première année d'abonnement offerte.
... Plus d'info sur http://complete.tiscali.be

Re: [parisc-linux] FC driver?

[Randolph Chung]

> >So your device is called "PCI_DEVICE_ID_HP_TACHYON". Searching for this
> >string, you'll find it in ./linux/drivers/scsi/cpqfcTSinit.c, so that
> >card seems to be supported.

well....

this is the "right" driver, but it doesn't work on parisc. Grant has
poked at it a little bit but afaik it still doesn't work. The driver is
not that well written either, so that doesn't help either :(

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

Re: [parisc-linux] FC driver?

[Grant Grundler]

On Mon, Mar 17, 2003 at 12:18:01PM +0100, Jan-Benedict Glaw wrote:
> So your device is called "PCI_DEVICE_ID_HP_TACHYON".

Please don't ever call a TachLite (TL) devices "Tachyon".
Tachyon (5000) was the first FC chip made by HP (now Agilent)
and was a nightmare to program. TachLite  (5100/5166)
had a simpler programming model and fewer bugs. TachLite XL2
chips (5200) use the same programming model.


> See, it's quite easy to see if a PCI card seems to be supported:-)

Yes, but sometimes it's easier to start with "lspci -n" output.

cpqfc code suggests it supports all Tachlite HBAs.
But it depends on GBIC/HBA configuration and HPUX folks haven't
been interested in making cpqfc work with their XL2 HBA.
Jes Sorensen/Martin Petersen did get older (5100/5166) TL HBAs
from HP working with cpqfc driver.

grant

Re: [parisc-linux] FC driver?

[Grant Grundler]

On Mon, Mar 17, 2003 at 07:52:35AM -0800, Randolph Chung wrote:
> this is the "right" driver, but it doesn't work on parisc. Grant has
> poked at it a little bit but afaik it still doesn't work.

I was trying to get XL2 HBAs working - and at least now I can load
and unload the driver on parisc. But XL2 is still not working.
I thought 5100/5166 (TL) HBAs did work.

> The driver is
> not that well written either, so that doesn't help either :(

If someone wants to take over maintaining cpqfc driver, I suspect
that would be a welcome request. Please let me know and I'll
forward to the right people in HP. (I've had this conversation
with the current maintainers already.)

grant

Re: [parisc-linux] FC driver?

[Ryan Bradetich]

On Mon, 2003-03-17 at 09:14, Grant Grundler wrote:
> On Mon, Mar 17, 2003 at 12:18:01PM +0100, Jan-Benedict Glaw wrote:
> > So your device is called "PCI_DEVICE_ID_HP_TACHYON".
> 
> Please don't ever call a TachLite (TL) devices "Tachyon".
> Tachyon (5000) was the first FC chip made by HP (now Agilent)
> and was a nightmare to program. TachLite  (5100/5166)
> had a simpler programming model and fewer bugs. TachLite XL2
> chips (5200) use the same programming model.
> 
> 
> > See, it's quite easy to see if a PCI card seems to be supported:-)
> 
> Yes, but sometimes it's easier to start with "lspci -n" output.
> 
> cpqfc code suggests it supports all Tachlite HBAs.
> But it depends on GBIC/HBA configuration and HPUX folks haven't
> been interested in making cpqfc work with their XL2 HBA.
> Jes Sorensen/Martin Petersen did get older (5100/5166) TL HBAs
> from HP working with cpqfc driver.

On parisc?  I've had trouble with it running on my C200.  Maybe
it is time to try it again.  I know Jes and Martin worked on it 
for i386..

Thanks,

- Ryan

> grant
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
-- 
Ryan Bradetich <rbradetich@uswest.net>

Re: [parisc-linux] FC driver?

[Jan-Benedict Glaw]

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

On Mon, 2003-03-17 09:21:05 -0700, Grant Grundler <grundler@dsl2.external.hp.com>
wrote in message <20030317162105.GB31378@dsl2.external.hp.com>:
> On Mon, Mar 17, 2003 at 07:52:35AM -0800, Randolph Chung wrote:
> > The driver is
> > not that well written either, so that doesn't help either :(
> 
> If someone wants to take over maintaining cpqfc driver, I suspect
> that would be a welcome request. Please let me know and I'll
> forward to the right people in HP. (I've had this conversation
> with the current maintainers already.)

:) Well, I don't have such a board, I don't have FC-HDDs, I don't even
have a 64bit/66MHz box. ...and looking over the code, it's somewhat
cruel:-) All over all scared^H^H^Httered with C++ish comments, silly
VARIABLE NAMES and it is *hugh*. Maintaining it, I suspect, is more like
rewriting it. Well, no hardware, no docs, ...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [parisc-linux] FC driver?

[Martin K. Petersen]

>>>>> "Ryan" == Ryan Bradetich <rbradetich@uswest.net> writes:

>> cpqfc code suggests it supports all Tachlite HBAs.  But it depends
>> on GBIC/HBA configuration and HPUX folks haven't been interested in
>> making cpqfc work with their XL2 HBA.  Jes Sorensen/Martin Petersen
>> did get older (5100/5166) TL HBAs from HP working with cpqfc
>> driver.

Ryan> On parisc?  I've had trouble with it running on my C200.  Maybe
Ryan> it is time to try it again.  I know Jes and Martin worked on it
Ryan> for i386..

I got a TL going on x86 way back.  Have not tried it on PA-RISC.

Also, the cpqfc driver could do with a serious cleanup.

I gave up beating it into shape and started working on a new driver.
But I'm swamped elsewhere and haven't touched it for a while.

-- 
Martin K. Petersen      http://mkp.net/

Re: [parisc-linux] FC driver?

[Grant Grundler]

On Mon, Mar 17, 2003 at 09:22:23AM -0700, Ryan Bradetich wrote:
> On parisc?  I've had trouble with it running on my C200.  Maybe
> it is time to try it again.  I know Jes and Martin worked on it 
> for i386..

my bad - you are right. It still doesn' work. Details follow.

I just tried it again with:
20:00.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02)
21:04.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel
Host Adapter (rev 0a)
21:05.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel
Host Adapter (rev 0a)

20:00.0 Class 0604: 1011:0026 (rev 02)
21:04.0 Class 0c04: 103c:1028 (rev 0a)
21:05.0 Class 0c04: 103c:1028 (rev 0a)

cpqfc driver loads but still finds no devices on the FC hub.

gsyprf11:~# modprobe cpqfc
 scsi_register allocating 6640 bytes for FC HBA
  HBA found!
  HostAdapter->PciDev->irq = 256
  PciDev->baseaddress[0]= 0
  PciDev->baseaddress[1]= 20000
  PciDev->baseaddress[2]= 20100
  PciDev->baseaddress[3]= fffffffffa040000
  cpqfcHBAdata->fcChip.Registers. :
    IOBaseL = 20000
    IOBaseU = 20100
 ioremap'd Membase: fffffffffa040000
    SFQconsumerIndex.address = fffffffffa040058
    ERQproducerIndex.address = fffffffffa040008
    TYconfig.address = fffffffffa040184
    FMconfig.address = fffffffffa0401c0
    FMcontrol.address = fffffffffa0401c4
  Requesting 255 I/O addresses @ 20000
  Requesting 255 I/O addresses @ 20100
 ResetTachyon
  HBA Tachyon RevId 2.2
Allocating 129024 for 576 Exchanges @ 00000000355e0000
Allocating 112904 for LinkQ @ 00000000355c0000 (576 elements)
Allocating 106504 for TachSEST for 512 Exchanges
  cpqfcTS: writing IMQ BASE 7580000h    PI 7584000h
  cpqfcTS: SEST 000000004be80000(virt): Wrote base 75A0000h @
fffffffffa040140
cpqfcTS: NVRAM read failed
 WARNING! HBA NVRAM WWN read failed - make alias
  WWN 51044F1044556677
  Waiting for broken Brocade switch...
 scsi_register allocating 6640 bytes for FC HBA
  HBA found!
  HostAdapter->PciDev->irq = 257
  PciDev->baseaddress[0]= 0
  PciDev->baseaddress[1]= 20200
  PciDev->baseaddress[2]= 20300
  PciDev->baseaddress[3]= fffffffffa041000
  cpqfcHBAdata->fcChip.Registers. :
    IOBaseL = 20200
    IOBaseU = 20300
 ioremap'd Membase: fffffffffa041000
    SFQconsumerIndex.address = fffffffffa041058
    ERQproducerIndex.address = fffffffffa041008
    TYconfig.address = fffffffffa041184
    FMconfig.address = fffffffffa0411c0
    FMcontrol.address = fffffffffa0411c4
  Requesting 255 I/O addresses @ 20200
  Requesting 255 I/O addresses @ 20300
 ResetTachyon
  HBA Tachyon RevId 2.2
Allocating 129024 for 576 Exchanges @ 000000004be60000
Allocating 112904 for LinkQ @ 000000004be40000 (576 elements)
Allocating 106504 for TachSEST for 512 Exchanges
  cpqfcTS: writing IMQ BASE 7800000h    PI 7804000h
  cpqfcTS: SEST 000000004be20000(virt): Wrote base 7820000h @
fffffffffa041140
cpqfcTS: NVRAM read failed
 WARNING! HBA NVRAM WWN read failed - make alias
  WWN 510450E844556677
  Waiting for broken Brocade switch...
scsi6 : Agilent FC HBA, Tachyon XL2 HPFC-5200B/2.2: WWN 51044F1044556677
 on PCI bus 33 device 0x1028 irq 256 IObaseL 0x20000, MEMBASE 0xfa040000
PCI bus width 64 bits, bus speed 66 MHz
FCP-SCSI Driver v2.1.1
GBIC detected: Unknown.  LPSM 0h Monitor
scsi7 : Agilent FC HBA, Tachyon XL2 HPFC-5200B/2.2: WWN 510450E844556677
 on PCI bus 33 device 0x1028 irq 257 IObaseL 0x20200, MEMBASE 0xfa041000
PCI bus width 64 bits, bus speed 66 MHz
FCP-SCSI Driver v2.1.1
GBIC detected: Short-wave.  LPSM 0h Monitor
gsyprf11:~#

The "NVRAM read failed" msg seems to be a problem still.
Fixing that would be a next step. The GBIC detection is the
next problem that would need work. Looks like a timing problem
since the first GBIC was not detected and the second one was.

grant

Re: [parisc-linux] FC driver?

[Jan-Benedict Glaw]

[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]

On Mon, 2003-03-17 17:34:30 +0100, Jan-Benedict Glaw <jbglaw@lug-owl.de>
wrote in message <20030317163430.GI17073@lug-owl.de>:
> On Mon, 2003-03-17 09:21:05 -0700, Grant Grundler <grundler@dsl2.external.hp.com>
> wrote in message <20030317162105.GB31378@dsl2.external.hp.com>:
> > On Mon, Mar 17, 2003 at 07:52:35AM -0800, Randolph Chung wrote:
> > > The driver is
> > > not that well written either, so that doesn't help either :(
> > 
> > If someone wants to take over maintaining cpqfc driver, I suspect
> > that would be a welcome request. Please let me know and I'll
> > forward to the right people in HP. (I've had this conversation
> > with the current maintainers already.)
> 
> :) Well, I don't have such a board, I don't have FC-HDDs, I don't even
> have a 64bit/66MHz box. ...and looking over the code, it's somewhat

Oh, I need to correct this. My Athlon does have 64bit PCI slots. Still,
no such PCI card, no FC hub/HDDs...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [parisc-linux] FC driver?

[Joel Soete]

Hi all,

Thanks a lot for all those info. 

Unfortunately I have no free time to help more on this driver (and also not
enough knowledge for the moment: even thought time and work could solve this
pb :) ).

Joel


>-- Original Message --
>To: Ryan Bradetich <rbradetich@uswest.net>
>Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
>	parisc-linux@lists.parisc-linux.org
>Subject: Re: [parisc-linux] FC driver?
>From: grundler@dsl2.external.hp.com (Grant Grundler)
>Date: Mon, 17 Mar 2003 09:38:04 -0700
>
>
>On Mon, Mar 17, 2003 at 09:22:23AM -0700, Ryan Bradetich wrote:
>> On parisc?  I've had trouble with it running on my C200.  Maybe
>> it is time to try it again.  I know Jes and Martin worked on it 
>> for i386..
>
>my bad - you are right. It still doesn' work. Details follow.
>
>I just tried it again with:
>20:00.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02)
>21:04.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel
>Host Adapter (rev 0a)
>21:05.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel
>Host Adapter (rev 0a)
>
>20:00.0 Class 0604: 1011:0026 (rev 02)
>21:04.0 Class 0c04: 103c:1028 (rev 0a)
>21:05.0 Class 0c04: 103c:1028 (rev 0a)
>
>cpqfc driver loads but still finds no devices on the FC hub.
>
>gsyprf11:~# modprobe cpqfc
> scsi_register allocating 6640 bytes for FC HBA
>  HBA found!
>  HostAdapter->PciDev->irq = 256
>  PciDev->baseaddress[0]= 0
>  PciDev->baseaddress[1]= 20000
>  PciDev->baseaddress[2]= 20100
>  PciDev->baseaddress[3]= fffffffffa040000
>  cpqfcHBAdata->fcChip.Registers. :
>    IOBaseL = 20000
>    IOBaseU = 20100
> ioremap'd Membase: fffffffffa040000
>    SFQconsumerIndex.address = fffffffffa040058
>    ERQproducerIndex.address = fffffffffa040008
>    TYconfig.address = fffffffffa040184
>    FMconfig.address = fffffffffa0401c0
>    FMcontrol.address = fffffffffa0401c4
>  Requesting 255 I/O addresses @ 20000
>  Requesting 255 I/O addresses @ 20100
> ResetTachyon
>  HBA Tachyon RevId 2.2
>Allocating 129024 for 576 Exchanges @ 00000000355e0000
>Allocating 112904 for LinkQ @ 00000000355c0000 (576 elements)
>Allocating 106504 for TachSEST for 512 Exchanges
>  cpqfcTS: writing IMQ BASE 7580000h    PI 7584000h
>  cpqfcTS: SEST 000000004be80000(virt): Wrote base 75A0000h @
>fffffffffa040140
>cpqfcTS: NVRAM read failed
> WARNING! HBA NVRAM WWN read failed - make alias
>  WWN 51044F1044556677
>  Waiting for broken Brocade switch...
> scsi_register allocating 6640 bytes for FC HBA
>  HBA found!
>  HostAdapter->PciDev->irq = 257
>  PciDev->baseaddress[0]= 0
>  PciDev->baseaddress[1]= 20200
>  PciDev->baseaddress[2]= 20300
>  PciDev->baseaddress[3]= fffffffffa041000
>  cpqfcHBAdata->fcChip.Registers. :
>    IOBaseL = 20200
>    IOBaseU = 20300
> ioremap'd Membase: fffffffffa041000
>    SFQconsumerIndex.address = fffffffffa041058
>    ERQproducerIndex.address = fffffffffa041008
>    TYconfig.address = fffffffffa041184
>    FMconfig.address = fffffffffa0411c0
>    FMcontrol.address = fffffffffa0411c4
>  Requesting 255 I/O addresses @ 20200
>  Requesting 255 I/O addresses @ 20300
> ResetTachyon
>  HBA Tachyon RevId 2.2
>Allocating 129024 for 576 Exchanges @ 000000004be60000
>Allocating 112904 for LinkQ @ 000000004be40000 (576 elements)
>Allocating 106504 for TachSEST for 512 Exchanges
>  cpqfcTS: writing IMQ BASE 7800000h    PI 7804000h
>  cpqfcTS: SEST 000000004be20000(virt): Wrote base 7820000h @
>fffffffffa041140
>cpqfcTS: NVRAM read failed
> WARNING! HBA NVRAM WWN read failed - make alias
>  WWN 510450E844556677
>  Waiting for broken Brocade switch...
>scsi6 : Agilent FC HBA, Tachyon XL2 HPFC-5200B/2.2: WWN 51044F1044556677
> on PCI bus 33 device 0x1028 irq 256 IObaseL 0x20000, MEMBASE 0xfa040000
>PCI bus width 64 bits, bus speed 66 MHz
>FCP-SCSI Driver v2.1.1
>GBIC detected: Unknown.  LPSM 0h Monitor
>scsi7 : Agilent FC HBA, Tachyon XL2 HPFC-5200B/2.2: WWN 510450E844556677
> on PCI bus 33 device 0x1028 irq 257 IObaseL 0x20200, MEMBASE 0xfa041000
>PCI bus width 64 bits, bus speed 66 MHz
>FCP-SCSI Driver v2.1.1
>GBIC detected: Short-wave.  LPSM 0h Monitor
>gsyprf11:~#
>
>The "NVRAM read failed" msg seems to be a problem still.
>Fixing that would be a next step. The GBIC detection is the
>next problem that would need work. Looks like a timing problem
>since the first GBIC was not detected and the second one was.
>
>grant
>_______________________________________________
>parisc-linux mailing list
>parisc-linux@lists.parisc-linux.org
>http://lists.parisc-linux.org/mailman/listinfo/parisc-linux


---------------------------------
Vous surfez avec une ligne classique ?
Economisez jusqu'à 25% avec Tiscali Complete !
Offre spéciale : première année d'abonnement offerte.
... Plus d'info sur http://complete.tiscali.be

Re: [parisc-linux] FC driver?

[Joel Soete]

Hi all,
>
>Thanks a lot for all those info. 
>
>Unfortunately I have no free time to help more on this driver (and also
not
>enough knowledge for the moment: even thought time and work could solve
this
>pb :) ).
>
Never the less I have a quick look and add some printk():
...
unsigned long cpqfcTS_ReadNVRAM( void* GPIOin, void* GPIOout , USHORT count,
	UCHAR *buf )
{
  unsigned short i;

  if( !( tl_i2c_tx_start(GPIOin, GPIOout) ))
    return FALSE;

    printk(">>> %s step1\n", __FUNCTION__);

  // Select the NVRAM for "dummy" write, to set the address
    printk(">>> GPIOout %p\n", GPIOout);
    printk(">>> SLAVE_WRITE_ADDRESS: %d\n", SLAVE_WRITE_ADDRESS);

  tl_i2c_tx_byte( GPIOout , SLAVE_WRITE_ADDRESS );
  if ( !tl_i2c_rx_ack(GPIOin, GPIOout ) )
    return( FALSE );

    printk("%s step2\n", __FUNCTION__);
...

and notice that the ReadNVRAM failed earlier (dmesg):

...
 scsi_register allocating 6640 bytes for FC HBA
  HBA found!
  HostAdapter->PciDev->irq = 320
  PciDev->baseaddress[0]= 0
  PciDev->baseaddress[1]= 30000
  PciDev->baseaddress[2]= 30100
  PciDev->baseaddress[3]= ffffffff88040000
  cpqfcHBAdata->fcChip.Registers. :
    IOBaseL = 30000
    IOBaseU = 30100
 ioremap'd Membase: ffffffff88040000
    SFQconsumerIndex.address = ffffffff88040058
    ERQproducerIndex.address = ffffffff88040008
    TYconfig.address = ffffffff88040184
    FMconfig.address = ffffffff880401c0
    FMcontrol.address = ffffffff880401c4
  Requesting 255 I/O addresses @ 30000
  Requesting 255 I/O addresses @ 30100
 ResetTachyon
  HBA Tachyon RevId 2.3
Allocating 129024 for 576 Exchanges @ 000000008d5c0000
Allocating 112904 for LinkQ @ 000000008d540000 (576 elements)
Allocating 106504 for TachSEST for 512 Exchanges
  cpqfcTS: writing IMQ BASE 500000h    PI 504000h
  cpqfcTS: SEST 0000000048b00000(virt): Wrote base 520000h @ ffffffff88040140
>>> cpqfcTS_ReadNVRAM step1
>>> GPIOout ffffffff88040188
>>> SLAVE_WRITE_ADDRESS: 160
cpqfcTS: NVRAM read failed
 WARNING! HBA NVRAM WWN read failed - make alias
  WWN 500723E644556677
  Waiting for broken Brocade switch...
 scsi_register allocating 6640 bytes for FC HBA
  HBA found!
  HostAdapter->PciDev->irq = 896
  PciDev->baseaddress[0]= 0
  PciDev->baseaddress[1]= c0000
  PciDev->baseaddress[2]= c0100
  PciDev->baseaddress[3]= ffffffffd4040000
  cpqfcHBAdata->fcChip.Registers. :
    IOBaseL = c0000
    IOBaseU = c0100
 ioremap'd Membase: ffffffffd4040000
    SFQconsumerIndex.address = ffffffffd4040058
    ERQproducerIndex.address = ffffffffd4040008
    TYconfig.address = ffffffffd4040184
    FMconfig.address = ffffffffd40401c0
    FMcontrol.address = ffffffffd40401c4
  Requesting 255 I/O addresses @ c0000
  Requesting 255 I/O addresses @ c0100
 ResetTachyon
  HBA Tachyon RevId 2.3
Allocating 129024 for 576 Exchanges @ 000000008d4c0000
Allocating 112904 for LinkQ @ 0000000048ee0000 (576 elements)
Allocating 106504 for TachSEST for 512 Exchanges
  cpqfcTS: writing IMQ BASE 640000h    PI 644000h
  cpqfcTS: SEST 000000008d5a0000(virt): Wrote base 660000h @ ffffffffd4040140
>>> cpqfcTS_ReadNVRAM step1
>>> GPIOout ffffffffd4040188
>>> SLAVE_WRITE_ADDRESS: 160
cpqfcTS: NVRAM read failed
 WARNING! HBA NVRAM WWN read failed - make alias
  WWN 500725B644556677
  Waiting for broken Brocade switch...
 scsi_register allocating 6640 bytes for FC HBA
  HBA found!
  HostAdapter->PciDev->irq = 960
  PciDev->baseaddress[0]= 0
  PciDev->baseaddress[1]= d0000
  PciDev->baseaddress[2]= d0100
  PciDev->baseaddress[3]= ffffffffd8040000
  cpqfcHBAdata->fcChip.Registers. :
    IOBaseL = d0000
    IOBaseU = d0100
 ioremap'd Membase: ffffffffd8040000
    SFQconsumerIndex.address = ffffffffd8040058
    ERQproducerIndex.address = ffffffffd8040008
    TYconfig.address = ffffffffd8040184
    FMconfig.address = ffffffffd80401c0
    FMcontrol.address = ffffffffd80401c4
  Requesting 255 I/O addresses @ d0000
  Requesting 255 I/O addresses @ d0100
 ResetTachyon
  HBA Tachyon RevId 2.3
Allocating 129024 for 576 Exchanges @ 00000000485c0000
Allocating 112904 for LinkQ @ 00000000487a0000 (576 elements)
Allocating 106504 for TachSEST for 512 Exchanges
  cpqfcTS: writing IMQ BASE 6C0000h    PI 6C4000h
  cpqfcTS: SEST 0000000048020000(virt): Wrote base 6E0000h @ ffffffffd8040140
cpqfcTS_ReadNVRAM step1
>>> GPIOout ffffffffd8040188
>>> SLAVE_WRITE_ADDRESS: 160
>>> cpqfcTS: NVRAM read failed
 WARNING! HBA NVRAM WWN read failed - make alias
  WWN 5007278544556677
  Waiting for broken Brocade switch...
scsi3 : Compaq FibreChannel HBA Tachyon Chip/Board Ver??: WWN 500723E644556677
 on PCI bus 32 device 0x1028 irq 320 IObaseL 0x30000, MEMBASE 0x88040000
PCI bus width 64 bits, bus speed 66 MHz
FCP-SCSI Driver v2.1.1
GBIC detected: NONE!  LPSM 0h Monitor
scsi4 : Compaq FibreChannel HBA Tachyon Chip/Board Ver??: WWN 500725B644556677
 on PCI bus 208 device 0x1028 irq 896 IObaseL 0xc0000, MEMBASE 0xd4040000
PCI bus width 64 bits, bus speed 66 MHz
FCP-SCSI Driver v2.1.1
GBIC detected: NONE!  LPSM 0h Monitor
scsi5 : Compaq FibreChannel HBA Tachyon Chip/Board Ver??: WWN 5007278544556677
 on PCI bus 224 device 0x1028 irq 960 IObaseL 0xd0000, MEMBASE 0xd8040000
PCI bus width 64 bits, bus speed 66 MHz
FCP-SCSI Driver v2.1.1
GBIC detected: NONE!  LPSM 0h Monitor

So it seems that   tl_i2c_tx_byte() failled?

Is GPIout are OK?

I have not any detailed doc about this card, so any advise is well come.

Thanks again,
    Joel


---------------------------------
Vous surfez avec une ligne classique ?
Economisez jusqu'à 25% avec Tiscali Complete !
Offre spéciale : première année d'abonnement offerte.
... Plus d'info sur http://complete.tiscali.be

Re: [parisc-linux] FC driver?

[Joel Soete]

Hi Grant,

Grant Grundler wrote:

>cpqfc driver loads but still finds no devices on the FC hub.
>
>  
>
Is a FC hub is required to expect to use this driver (under hpux we used 
this card directly connected to fc of a XP512 diskarray)?

Thanks,
    Joel

Re: [parisc-linux] FC driver?

[Grant Grundler]

On Sat, Mar 22, 2003 at 09:58:59PM +0000, Joel Soete wrote:
> Is a FC hub is required to expect to use this driver (under hpux we used 
> this card directly connected to fc of a XP512 diskarray)?

I don't think so. I just happen to have the couple of disks/hosts all
connected to a pair of hubs.

grant

Re: [parisc-linux] FC driver?

[Joel Soete]

>-- Original Message --
>Date: Sat, 22 Mar 2003 23:24:54 -0700
>To: Joel Soete <joel.soete@tiscali.be>
>Cc: parisc-linux@lists.parisc-linux.org
>Subject: Re: [parisc-linux] FC driver?
>From: grundler@dsl2.external.hp.com (Grant Grundler)
>
>
>On Sat, Mar 22, 2003 at 09:58:59PM +0000, Joel Soete wrote:
>> Is a FC hub is required to expect to use this driver (under hpux we used
>
>> this card directly connected to fc of a XP512 diskarray)?
>
>I don't think so. I just happen to have the couple of disks/hosts all
>connected to a pair of hubs.

Ah ok (but as I have no doc I do not progress a lot and so still hoppe answer
from Martin :)

Thanks,
    Joel


---------------------------------
Vous surfez avec une ligne classique ?
Economisez jusqu'à 25% avec Tiscali Complete !
Offre spéciale : première année d'abonnement offerte.
... Plus d'info sur http://complete.tiscali.be