lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 4 Apr 2007 02:36:37 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	David Miller <davem@...emloft.net>
Cc:	paulus@...ba.org, dwmw2@...radead.org, linuxppc-dev@...abs.org,
	benh@...nel.crashing.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers.

> Using different majors for different instances of the exact same kind
> of device is really not smart.  It's a serial port, and if you try
> to dress it up to be something else you run into all kinds of problems.

Disagree. There are lots of good reasons you need to know which
port/which card/which slot/which multiplexor.

There is a world of a difference between a serious serial port
application and "wtf has my console gone"

> Not the least of which is the user has to scratch his head figuring
> out what kind of chip drives his serial console, he just wants the
> first serial port and he should have a way to say just that even
> on the kernel command line.

Define "first". First by I/O order, by PCI scan order (and which type),
does ACPI come before or after ISA etc...

At the moment we sort of magic this for the PC by having hardcoded probe
order hacks by address, on the sparc by having other driver magic, on the
PPC by hardcoding some rules etc then hack the result to be ttyS0.

I've no fundamental problem with S0->console port 1, S1 -> console port 2
etc, but the general notion that type and positional information doesn't
matter is complete and utter bollocks when you try and apply it to any
serious serial setup.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ