public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Sym53c8xxx woes
Date: Sat, 23 Mar 2002 00:20:37 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905333@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905332@msgid-missing>

Hi Aaron,

I guess the compile error would be caused due to no definition
of dma64_addr_t. right?
I that case, you can make a kernel with setting "DMA addressing mode"
to be 0. DMA 64bit mode for Sym53c8xx won't work on AzusA, anyway.

Regards,
Kimi


On Fri, 22 Mar 2002 15:40:48 -0800 (PST)
Aaron Burt <aaron@osdl.org> wrote:

> OK, so I've upgraded our NEC AzusA 16-way to 2.4.18, and ran into a li'l
> problem.  When I've 20GB of RAM or more enabled, the Sym53c8xxx v1 driver
> crases on boot.  The v2 driver won't even compile.
> 
> Luckily, the SCSI drives are all on a qla1280 controller, so I can simply
> leave the Symbios support out, but still this is a problem.
> 
> Without the Symbios driver, I can run it with all 16 procs and 32GB ram.
> 
> ObPlug: Our 16-way is available to all and sundry, and I'm currently
> bringing up a couple of 4-way Lions as well.  A couple 2-ways are in the
> pipeline.
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>



      parent reply	other threads:[~2002-03-23  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 23:40 [Linux-ia64] Sym53c8xxx woes Aaron Burt
2002-03-23  0:16 ` Grant Grundler
2002-03-23  0:20 ` Kimio Suganuma [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590701905333@msgid-missing \
    --to=k-suganuma@mvj.biglobe.ne.jp \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox