Is there anyone who is succesfully using SCSI devices connected to MESH SCSI
with 2.4.0-test1 (or late 2.3.99-preX, e.g. pre9)?
I do, everything is detected fine, I use
Linux version 2.4.0-test1-ac4 (root@ma1311) (gcc version 2.95.2 19991024
(release/franzo))
The ac1 version I tried before worked aswell. dmesg looks like:
mesh: target 0 synchronous at 10.0 MB/s
Vendor: QUANTUM Model: FIREBALL_TM3200S Rev: 300X
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi1, channel 0, id 0, lun 0
mesh: target 1 synchronous at 10.0 MB/s
Vendor: MICROP Model: 4345NS Rev: x43h
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi1, channel 0, id 1, lun 0
mesh: target 3 synchronous at 10.0 MB/s
Vendor: PLEXTOR Model: CD-ROM PX-32TS Rev: 1.03
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi1, channel 0, id 3, lun 0
scsi : detected 1 SCSI cdrom 2 SCSI disks total.
Mounting a crdrom doesen't work for me either,
mount -t hfs /dev/cdrom /mnt/cdrom yields:
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
or too many mounted file systems
Cheers
Henning
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Is there anyone who is succesfully using SCSI devices connected to MESH SCSI
with 2.4.0-test1 (or late 2.3.99-preX, e.g. pre9)?
I do, everything is detected fine, I use
Linux version 2.4.0-test1-ac4 (root@ma1311) (gcc version 2.95.2 19991024
(release/franzo))
Hmm... I just tried a kernel without support for my sym53c875, and that didn't
work either, so it's not a multiple SCSI adapter issue. During SCSI device
probing, it just waits 30 seconds and doesn't find anything.
The weird thing is that the MESH driver didn't change. Let's enable debugging
and retry...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi,
trying to fix my console character displayment I wonder whether I'm
looking at the right place ?????
When in the console with 8bpp, fbcon-cfb8.c is the driver the kernel uses
right? Not the tdfxfb driver for the card?
Cheers
Henning
--------------------------------------------------------------------------
Henning Loeser Fachbereich Physik
email: henning.loeser@physik.uni-marburg.de AG Oberflaechen
Philipps-Uni Marburg
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
trying to fix my console character displayment I wonder whether I'm
looking at the right place ?????
When in the console with 8bpp, fbcon-cfb8.c is the driver the kernel uses
right? Not the tdfxfb driver for the card?
Tdxfb is accelerated. So unless you disable acceleration, it uses the
operations in fbcon_banshee8 in tdxfb.c:
info->dispsw = noaccel ? fbcon_cfb8 : fbcon_banshee8
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
trying to fix my console character displayment I wonder whether I'm
looking at the right place ?????
When in the console with 8bpp, fbcon-cfb8.c is the driver the kernel uses
right? Not the tdfxfb driver for the card?
Tdxfb is accelerated. So unless you disable acceleration, it uses the
operations in fbcon_banshee8 in tdxfb.c:
info->dispsw = noaccel ? fbcon_cfb8 : fbcon_banshee8
Gr{oetje,eeting}s,
Geert
Thanks, if I simply make it call fbcon-cfb8 no matter what the font
appears correctly. So I guess what I have to acctually do is to fix the
'do_putc' and 'do_putcs' functions in tdfxfb.c to diplay BIGENDIAN
characters correctly.
That's what your nibbletab_cfb8 does in fbcon-cfb8 right?
Henning
--------------------------------------------------------------------------
Henning Loeser Fachbereich Physik
email: henning.loeser@physik.uni-marburg.de AG Oberflaechen
Philipps-Uni Marburg
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
trying to fix my console character displayment I wonder whether I'm
looking at the right place ?????
When in the console with 8bpp, fbcon-cfb8.c is the driver the kernel uses
right? Not the tdfxfb driver for the card?
Tdxfb is accelerated. So unless you disable acceleration, it uses the
operations in fbcon_banshee8 in tdxfb.c:
info->dispsw = noaccel ? fbcon_cfb8 : fbcon_banshee8
Thanks, if I simply make it call fbcon-cfb8 no matter what the font
appears correctly. So I guess what I have to acctually do is to fix the
'do_putc' and 'do_putcs' functions in tdfxfb.c to diplay BIGENDIAN
characters correctly.
Yes. Perhaps the graphics accelerator has a flag to specify to use big endian
mode, and this flag isn't set?
That's what your nibbletab_cfb8 does in fbcon-cfb8 right?
Yes.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/