On 05/06/2015 02:34 AM, Hänel-Baas, Alexander wrote: > Hi, > > thanks four your reply. > >> The right way to handle this would be to create a symlink in a udev script (or rc.d scripts if you don't have/use udev). >> Regards, >> Peter Hurley > >> Why not just change it in userspace using a tool like udev? Don't force the kernel to do something like this. >> thanks, >> greg k-h > > I have played with udev and yes i can create a symlink when the 8250_pci.ko is load. > But this is not the right solution for my problem: > > My System has a SIO-Uart pluggable over the PLC-Bus and a PCI ValleyView HSUART connected over the pci-bus. > > So the tty enumeration look like this: > SIO-UART -> ttyS0 -> this is the kernel console > -> ttyS1 > PCI-HSUART -> ttyS2 -> this is the console that can use by the userspace program > -> ttyS3 > > Case 2: the SIO-Uart is not connected. > PCI-HSUART -> ttyS0 -> and now the kernel prompt message and the userspace program too > -> ttyS1 It's not clear to me what you want to have happen in case 2. > In this case I need a free tty device for the PCI-HSUART and so I hope I can changed the device name only for the 8250_pci device to do this. > > Any ideas what can I do? > > Regards, > Alexander > > -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
