From: Otto Solares <solca@guug.org>
To: linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org, debian-sparc@lists.debian.org
Subject: sparc scsi esp depends on pci & hangs on boot
Date: Mon, 21 Jul 2003 20:51:42 -0600 [thread overview]
Message-ID: <20030722025142.GC25561@guug.org> (raw)
Hi ppl,
just reporting on 2.6.0-test1 on sparcs:
i am trying to compile linux-2.6.0-test1-{mm1,mm2,ac1,ac2)
on 2 differents sparcs, both latest debian sid & gcc-3.2.3:
ultra enterprise 1 (sun4u sparc64)
sparc station 4 (sun4m sparc32)
on both i need to enable PCI support even
when these boxes doesn't have a PCI bus,
i think the main bus is SBUS and i get
errors when compiling the Sun ESP scsi
controller about functions for DMA depending
on PCI. I don't think is convenient for
these old boxes having support for PCI
because enlarge the kernel and it really
doesn't have that type of bus.
And when i enable PCI support the sparc32
compiles fine but hangs inmediately on boot.
The sparc64 doesn't compile with ac2 patch:
arch/sparc64/kernel/built-in.o(.init.text+0x3bcc): In function `pdev_cookie_fillin':
: referencia a `pci_remove_bus_device' sin definir
make: *** [vmlinux] Error 1
The others mentioned kernels hangs when booting.
Yes, i have selected proper configuration for the
CONFIG_INPUT_*=y layer, CONFIG_VT_CONSOLE=y,
CONFIG_HW_CONSOLE=y and CONFIG_PROM_CONSOLE=y.
I even tried both CONFIG_FRAMEBUFFER_CONSOLE set to y/n
Any help will be apreciated as i really want
the 2.6 kernels support both sparc32 and sparc64
boxes, googling i found osinvestor.com/sparc but
is down and in the sparclinux archives there are
patches but they appear to be applied on linus
2.6.0-test1 kernel.
Thanks.
-solca
next reply other threads:[~2003-07-22 2:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 2:51 Otto Solares [this message]
2003-07-22 12:09 ` sparc scsi esp depends on pci & hangs on boot Pete Zaitcev
2003-07-22 18:26 ` Otto Solares
2003-07-23 0:54 ` David S. Miller
2003-07-23 2:32 ` Otto Solares
2003-07-23 6:07 ` Christoph Hellwig
2003-07-23 6:24 ` David S. Miller
2003-07-23 6:28 ` Christoph Hellwig
2003-07-23 6:29 ` David S. Miller
2003-07-23 6:40 ` Christoph Hellwig
2003-07-23 6:57 ` David S. Miller
2003-07-23 7:02 ` Christoph Hellwig
2003-07-23 7:20 ` David S. Miller
2003-07-23 8:45 ` Otto Solares
2003-07-23 14:42 ` Geert Uytterhoeven
2003-07-23 6:43 ` Otto Solares
2003-07-23 7:04 ` Christoph Hellwig
2003-07-23 7:20 ` Otto Solares
2003-07-23 7:27 ` David S. Miller
2003-07-23 8:33 ` C.Newport
2003-07-23 8:28 ` David S. Miller
2003-07-23 9:35 ` C.Newport
2003-07-23 9:37 ` David S. Miller
2003-07-23 8:55 ` Otto Solares
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=20030722025142.GC25561@guug.org \
--to=solca@guug.org \
--cc=debian-sparc@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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