Ben:
> I'd be interested to know if the following (approximative)
> patch works for you from the original driver (typed directly in the
> mailer ;):
>
> static void mesh_init(struct mesh_state *ms)
> {
[... guts snipped ...]
> }
>
> Does it work for you ?
>
Yes, it works. Thank you.
Th
>
>After applying the patch from velco, my mesh_init looks like this:
>
>static void mesh_init(struct mesh_state *ms)
>{
>volatile struct mesh_regs *mr = ms->mesh;
>volatile struct dbdma_regs *md = ms->dma;
>
>udelay(100);
>
>out_8(&mr->exception, 0xff); /* clear all exception
Benjamin Herrenschmidt wrote:
;; >- out_le32(&md->control, (RUN|PAUSE|FLUSH|WAKE) << 16); /* stop dma */
;;
;; What about waiting for the DBDMA channel to actually stop ?
;; You should spin loop until the channel is actually stopped here.
;;
;; Note also that due to PCI write posting, doing a
Momchil Velikov wrote:
> You may try the following patch. It worked for me.
>
> [... patch snipped ...]
Beautiful! Thank you!
I threw in your patch onto mesh.c from 2.2.17 source (bad idea?)
and compiled the whole kernel (i'll make it a module next time)
and it seems to work fine:
mesh: target
>- out_le32(&md->control, (RUN|PAUSE|FLUSH|WAKE) << 16); /* stop dma */
What about waiting for the DBDMA channel to actually stop ?
You should spin loop until the channel is actually stopped here.
Note also that due to PCI write posting, doing an out_xxx, followed by a
udelay, may not work
Takehiko Abe wrote:
>
> Michel Lanners wrote:
>
> > Try putting your Fireball on a different ID. This was FAQ a very long
> > time ago when MkLinux started supporting the 7/8/9x00 PCI-based
> > machines... Nobody ever came up with any sort of explanation, but moving
> > the disk to a different SC
Michel Lanners wrote:
> Try putting your Fireball on a different ID. This was FAQ a very long
> time ago when MkLinux started supporting the 7/8/9x00 PCI-based
> machines... Nobody ever came up with any sort of explanation, but moving
> the disk to a different SCSI ID helped most of the time.
Unf
On 18 Dec, this message from Takehiko Abe echoed through cyberspace:
> I keep getting the follwing message at the boot time.
>
> scsi0 : MESH
> scsi1 : 53C94
> scsi : 2 hosts.
> mesh: target 0 aborted
>
> The aborted target 0 is a HFS formatted internal scsi HD
> (quantum firebal
On Mon, 18 Dec 2000, Takehiko Abe wrote:
> I keep getting the follwing message at the boot time.
>
> scsi0 : MESH
> scsi1 : 53C94
> scsi : 2 hosts.
> mesh: target 0 aborted
> mesh: target 1 synchronous at 10.0 MB/s
> Vendor: nEC Model: DSE2100S Rev: 0306
>
I keep getting the follwing message at the boot time.
scsi0 : MESH
scsi1 : 53C94
scsi : 2 hosts.
mesh: target 0 aborted
mesh: target 1 synchronous at 10.0 MB/s
Vendor: nEC Model: DSE2100S Rev: 0306
...
The aborted target 0 is a HFS formatted internal
10 matches
Mail list logo
