Re: OXFW 911 problems

HI again,

Just wanted to notify you that i'm dropping my efforts in trying to get
it to work with the latest ieee1394 drivers.
As i only needed the sbp2 driver to work i will settle with using the
2.6.2 drivers in the 2.6.7 kernel since it seems to be stable.
I have been running a testcopy now for about 19 hours and i have not
noticed any datacorruption..

A thing that i notice (that might be the problem) is that here on the
device is that in the dmesg you can see that it detects that the max_rom
is 4 as it should:
ieee1394: NodeMgr: raw=0x00ff5002 irmc=0 cmc=0 isc=0 bmc=0 pmc=0
cyc_clk_acc=255 max_rec=64 max_rom=4 gen=0 lspd=2
But if you check the bus_options in the /sys fs you can see that it
reports the maxrom as 0.
IRMC(0) CMC(0) ISC(0) BMC(0) PMC(0) GEN(0) LSPD(2) MAX_REC(64)
MAX_ROM(0) CYC_CLK_ACC(255)
 
Not shure why it reports this in this way, or even if it's a bug.

Btw, I have got access to the 1394-1995 and 1394a-2000 IEEE standards
documents, if anyone needs some specific information from them feel free
to contact me.

/Patric

On Thu, 2004-08-19 at 00:15, Patric wrote:
> Just got it to work here...
>
> sbp2: $Rev: 1096 $ Ben Collins <bcollins@debian.org>
> ohci1394: $Rev: 1097 $ Ben Collins <bcollins@debian.org>
> ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19]
> MMIO=[d2007000-d20077ff] Max Packet=[2048]
> ieee1394: Host added: ID:BUS[0-00:1023] GUID[00508b08800370fe]
> ieee1394: Node added: ID:BUS[0-01:1023] GUID[0030e001ee911099]
> ieee1394: The root node is not cycle master capable; selecting a new
> root node and resetting...
> ieee1394: Node changed: 0-01:1023 -> 0-00:1023
> ieee1394: Node changed: 0-00:1023 -> 0-01:1023
> scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
> ieee1394: sbp2: Logged into SBP-2 device
> ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
> Vendor: HDS72251 Model: 6VLAT20 Rev:
> Type: Direct-Access ANSI SCSI revision: 06
> SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
> sda: asking for cache data failed
> sda: assuming drive cache: write through
> /dev/scsi/host0/bus0/target0/lun0: p1
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
> ieee1394: sbp2: Logged into SBP-2 device
> ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
> Vendor: HDS72251 Model: 6VLAT20 Rev:
> Type: Direct-Access ANSI SCSI revision: 06
> SCSI device sdb: 321672960 512-byte hdwr sectors (164697 MB)
> sdb: asking for cache data failed
> sdb: assuming drive cache: write through
> /dev/scsi/host0/bus0/target1/lun0: p1
> Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
> Attached scsi generic sg1 at scsi0, channel 0, id 1, lun 0, type 0
>
> It's now atleast verified that it's only the ieee1394 path that causes
> this problem.
>
> What i did was that i got the drivers/ieee1394 folder from a 2.6.2
> kernel and replaced the ieee1394 folder in the 2.6.7 kernel.
>
> then patch the file ieee1394_types.h
> since we dont have CLEAR_BITMAP function in 2.6.7.
>
> so in here:
> #define HPSB_TPOOL_INIT(_tp) \
> do { \
> CLEAR_BITMAP((_tp)->pool, 64); \
> spin_lock_init(&(_tp)->lock); \
> (_tp)->next = 0; \
> (_tp)->allocations = 0; \
> sema_init(&(_tp)->count, 63); \
> } while (0)
>
> replace CLEAR_BITMAP with:
> memset((_tp)->pool, 0, BITS_TO_LONGS(64)*sizeof(unsigned long));
>
> Also since there are a couple of more functions that are not accessible
> from 2.6.7 any more i managed to compile this with the current settings:
> <M> IEEE 1394 (FireWire) support (EXPERIMENTAL)
> <M> OHCI-1394 support
> <M> SBP-2 support (Harddisks etc.)
>
> Since cdev_unmap among other functions are removed from the 2.6.7 kernel
> you cannot include anything like raw1394 and those... But atleast we got
> something to go on from here and maybe create some patch...
>
> Thoe, i'm not to good at kernel stuff so dont expect anything soon, or
> even stable :D
>
> Not shure how stable this is, but give it a try if you feel daring :D
>
>
> /Patric
>
>
>
>
>
> On Wed, 2004-08-18 at 20:27, Andreas Klauer wrote:
> > Am Thursday 19 August 2004 00:01 schrieb Patric:
> > > I have tried this on the following kernels, same results on all.
> >
> > Try 2.4.20, 2.4.18 or (if you prefer 2.6.x series) 2.6.2. I've got
> > *exactly* the same problem as you do, but in these kernels it works (at
> > least for me). I reported this quite some time ago, but unfortunately,
> > nobody came up with a solution so far.
> >
> > HTH
> > Andreas
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> > _______________________________________________
> > mailing list Linux1394-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux1394-user
> >
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> mailing list Linux1394-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux1394-user
>

-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user
Received on Thu Aug 19 18:56:32 2004