Re: [PATCH 2.6] Altix serial driver

From: Chris Wedgwood (cw_at_f00f.org)
Date: 06/28/04

  • Next message: Clemens Schwaighofer: "Re: 2.6.7 and khelper" 
    Date: 	Sun, 27 Jun 2004 17:33:11 -0700
To: Erik Jacobson <erikj@subway.americas.sgi.com>

    On Sun, Jun 27, 2004 at 07:24:34PM -0500, Erik Jacobson wrote:

    > Maybe you can help me clear it up then. When I feed serial core the
    > name ttyS with TTY_MAJOR and minor 64, the registration fails. If I
    > disable 8250 in the kernel config, the registration works for us.

    I'm not sure why the 8250 code reserves/registers ttyS0 on Altix when
    do such hardware exists. I vaguely recall patching it to prevent this
    in a hacky way.

    I would like to know why the 8250 code is registering a driver for
    hardware that doesn't exist and see that fixed.

    > 1) You think we can some how use ttySX with our driver. I need more
    > information for that as I couldn't get it to work with serial
    > core.

    You can, I did this. It was probably a horrible hack, I really can't
    recall anymore. I don't know if that code ever got out or what
    happened to it. Maybe there are some PVs about it somewhere? I'm
    pretty sure the patches got sent out for vendor inclusion.

    I would simply find out why the 8250 driver is preventing a
    registration for you and go down that path.

    The other issue is what if someone puts a serial-port/modem card in an
    Altix so you do have 8250/16550-like hardware? I'm not sure that's
    sensible though and they probably deserves to break.

    I guess in general you have a bigger problem though, you can have tens
    of serial ports on a large system and if you want to support them all
    (or have the option of doing so) something more sensible needs to be
    figure out.

      --cw
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Clemens Schwaighofer: "Re: 2.6.7 and khelper"

    Relevant Pages

    • Re: VIA SATA I/O errors
      ... > and a lot of SCSI error messages will be output to the console. ... > few instances of this happening (which requires a hard power-off, ... I have no idea whether this is a software or hardware ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Patricks Test9 suspend code.
      ... > usb and agp were both compiled in to the kernel that worked. ... > never seemed to be dying due to the HARDWARE, it always shut all the hardware ... You really should try without AGP. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test9 - poor swap performance on low end machines
      ... hardware and in the way we use computers (interactive, Client/Server, ... fixing it in hardware by adding RAM works ... What we _can_ do in software, though, is prevent thrashing as long as ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.4 vs 2.6
      ... -- drivers for my telephony card are not 2.6-ready, ... So please be careful when making statements like that. ... have a narrow range of hardware on which the 2.6 kernel has actually ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: New mobo question
      ... >> I've ordered a new mobo as I'm having what appears to be data bus ... As far as I read him, he wants to build a kernel that runs on his new ... he has to just compile a kernel that includes hardware ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)