Re: [RFC 0/5] tty: move stuff around

Arnd Bergmann
2010-08-31T09:26:55Z

On Tuesday 31 August 2010, Alan Cox wrote:
> > drivers/char/tty_* -> tty/*
> > drivers/char/{vt stuff} -> tty/vt/
> > drivers/char/hvc_* -> drivers/tty/hvc/hvc_*
> > drivers/serial/* -> drivers/tty/serial/*
>
> There are dead bits in there too we should prune 68xxx stuff mostly

Geert, can you comment on the 68k serial drivers? Which
ones are to stay, which ones can get phased out?

> > drivers/usb/serial -> drivers/usb/serial
> >
> > cyclades,moxa,mxser -> drivers/tty/hw/
> >
> > stallion,istallion,
> > epca,specialix,ip2,
> > riscom,isicom -> drivers/staging/tty/*
>
> isicom has users and gets tested a bit, not sure about ip2/specialix.

I'll leave isicom then.

Specialix is marked in MAINTAINERS as supported by Roger, ip2
is maintained by Michael, maybe they have a preference for their
drivers.

Both drivers have a web page that is ~10 years old, which hints
that there is probably not much new hardware around.

> > generic_serial,vme_scc,
> > ser_a2232,sx,rio -> drivers/staging/generic_serial/*
> >
> > amiserial,nozomi,
> > serial167,synclink -> drivers/tty/hw (?)
>
> Why /hw - its a tty driver so drivers/tty - the non hw stuff is now in
> tty/

Right, makes sense.

> serial167 is dead/staging stuff, synclink* are used

ok

> > bfin_jtag_comm -> drivers/tty/hvc/hvc_bfin_jtag (?)
>
> Nothing to do with hvc

Not yet ;-)

You didn't reply to my question why it couldn't be. I'll let Mike
judge this one when he has looked at the hvc infrastructure.

I wouldn't move it to that directory unless the code gets changed
first, but I wanted to write down where I think it should end up.

> > rocket,ipwireless -> drivers/staging/tty/* (?)
>
> Rocket is used, ipwireless I think is also used

ok.

Arnd