[lkml]   [2010]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Fix Winbond CIR driver initialisation
    On Sun, Nov 07, 2010 at 03:46:48PM +0000, Alan Cox wrote:
    > > A workaround is to boot with argument 8250.nr_uarts=1. This is not really
    > > desirable, so this patch makes ttyS1 go away.
    > setserial can also be used for this surely ?

    That's about as user-unfriendly as the boot option.

    > > + dev_info(device, "Unregistering phony serial port ttyS1\n");
    > > + serial8250_unregister_port(1);
    > > + ok = request_region(data->sbase, SP_IOMEM_LEN, DRVNAME);
    > That's a hack that is only going to work on specific systems where it is
    > mapped the way you expect and doing stuff behind the back of the serial
    > driver.
    > I'm not averse to a better solution but it needs to be general and
    > maintainable. Is there a way to identify the presence of the windbond CIR
    > device as opposed to an 8250 ?

    Not sure which kind of identification you're looking for but would a PNP
    id be sufficient?

    David Härdeman
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2010-11-07 20:03    [W:0.030 / U:7.328 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site