On Wed, Sep 27, 2000 at 02:48:47PM -0700, H. Peter Anvin wrote:
> The only thing I'm not sure is that I believe the SPARC people uses
> ttyS* for Zilog 8530-based serial ports. I don't know if we want to
> define this as NS8250-family serial ports in light of that; I more
> tended to think of
From: "H. Peter Anvin" <[EMAIL PROTECTED]>
> Does that mean SPARC has a conflict between the 8250/16x50 driver and the
> Zilog driver? If so, the latter should probably move (ttyZ is still an
> unused name.)
If there's a conflict it would be with the minor numbers, which
I haven't been able to
Stuart MacDonald wrote:
>
> From: "Alan Cox" <[EMAIL PROTECTED]>
> > > The only thing I'm not sure is that I believe the SPARC people uses
> > > ttyS* for Zilog 8530-based serial ports. I don't know if we want to
> > > define this as NS8250-family serial ports in light of that; I more
> > >
Stuart MacDonald wrote:
From: "Alan Cox" [EMAIL PROTECTED]
The only thing I'm not sure is that I believe the SPARC people uses
ttyS* for Zilog 8530-based serial ports. I don't know if we want to
define this as NS8250-family serial ports in light of that; I more
tended to think of
> Yes you should be able to mix 16x50 chips with sa1100 chips. That is not the
> issue. I believe that people can place any mixture of IC's on a PCB.
Letting it make sense is another issue. Placing a Z80 next to an AMD
Irongate doesn't make sense to me...
> > HPA can I suggest the description
On Wed, Sep 27, 2000 at 06:03:30PM -0400, George France wrote:
>
> Please also read Mike Touloumtzis [[EMAIL PROTECTED]] posting in the
> arm-linux-kernel archives. He gets the concept.
Maybe I do, but I thought I was agreeing with Russell :-). Which
only serves to underscore the silliness of
} The only thing I'm not sure is that I believe the SPARC people uses
} ttyS* for Zilog 8530-based serial ports. I don't know if we want to
} define this as NS8250-family serial ports in light of that; I more
} tended to think of it as the "default" serial port for the
} architecture.
}
} It's
TECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: Russell King forks ARM Linux.u
>
>
> > So now we will have to send our patches to the kernel
> mailing list, setup
> > out own mailing list and web pages. It is not a problem
> s
> So now we will have to send our patches to the kernel mailing list, setup
> out own mailing list and web pages. It is not a problem since we already
> have a web site setup.
Personally I'd rather you accepted that everyone else agrees with Russell about
the major/minor issue and that -both-
> The only thing I'm not sure is that I believe the SPARC people uses
> ttyS* for Zilog 8530-based serial ports. I don't know if we want to
> define this as NS8250-family serial ports in light of that; I more
> tended to think of it as the "default" serial port for the
> architecture.
>
> It's
> > believe that no problem can be solved with a flame war
> going on. That is why
> > I decide to stop speaking with him about the serial port
> issue. He then
> > decided to block the e-mails. So here we are.
>
> Well if you arent speaking to him, then it doesnt matter if
> he blocks your
>
Followup to: <[EMAIL PROTECTED]>
By author:Alan Cox <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> I can see where his confusion arises, but yes you are right, people need to be
> able to mix the 16x50 driver with the sa1100 driver. The ppc people went through
> fixing this.
>
>
Hello Alan;
> I can see where his confusion arises, but yes you are right,
> people need to be
> able to mix the 16x50 driver with the sa1100 driver. The ppc
> people went through
> fixing this.
Yes you should be able to mix 16x50 chips with sa1100 chips. That is not the
issue. I believe
> believe that no problem can be solved with a flame war going on. That is why
> I decide to stop speaking with him about the serial port issue. He then
> decided to block the e-mails. So here we are.
Well if you arent speaking to him, then it doesnt matter if he blocks your
emails..
Alan
-
To
Followup to: <[EMAIL PROTECTED]>
By author:Alan Cox <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> > > So is there a URL with the whole discussion on. It looks like a fun read ?
> > Have a look at the linux-arm-kernel archive at
> >
> > So is there a URL with the whole discussion on. It looks like a fun read ?
> Have a look at the linux-arm-kernel archive at
> http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/
I can see where his confusion arises, but yes you are right, people need to be
able to mix the 16x50 driver
So is there a URL with the whole discussion on. It looks like a fun read ?
Have a look at the linux-arm-kernel archive at
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/
I can see where his confusion arises, but yes you are right, people need to be
able to mix the 16x50 driver
Followup to: [EMAIL PROTECTED]
By author:Alan Cox [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
So is there a URL with the whole discussion on. It looks like a fun read ?
Have a look at the linux-arm-kernel archive at
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/
I
Hello Alan;
I can see where his confusion arises, but yes you are right,
people need to be
able to mix the 16x50 driver with the sa1100 driver. The ppc
people went through
fixing this.
Yes you should be able to mix 16x50 chips with sa1100 chips. That is not the
issue. I believe that
believe that no problem can be solved with a flame war going on. That is why
I decide to stop speaking with him about the serial port issue. He then
decided to block the e-mails. So here we are.
Well if you arent speaking to him, then it doesnt matter if he blocks your
emails..
Alan
-
To
Followup to: [EMAIL PROTECTED]
By author:Alan Cox [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
I can see where his confusion arises, but yes you are right, people need to be
able to mix the 16x50 driver with the sa1100 driver. The ppc people went through
fixing this.
HPA can I
believe that no problem can be solved with a flame war
going on. That is why
I decide to stop speaking with him about the serial port
issue. He then
decided to block the e-mails. So here we are.
Well if you arent speaking to him, then it doesnt matter if
he blocks your
emails..
I
The only thing I'm not sure is that I believe the SPARC people uses
ttyS* for Zilog 8530-based serial ports. I don't know if we want to
define this as NS8250-family serial ports in light of that; I more
tended to think of it as the "default" serial port for the
architecture.
It's mostly
So now we will have to send our patches to the kernel mailing list, setup
out own mailing list and web pages. It is not a problem since we already
have a web site setup.
Personally I'd rather you accepted that everyone else agrees with Russell about
the major/minor issue and that -both- of
} The only thing I'm not sure is that I believe the SPARC people uses
} ttyS* for Zilog 8530-based serial ports. I don't know if we want to
} define this as NS8250-family serial ports in light of that; I more
} tended to think of it as the "default" serial port for the
} architecture.
}
} It's
PROTECTED];
[EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: Russell King forks ARM Linux.u
So now we will have to send our patches to the kernel
mailing list, setup
out own mailing list and web pages. It is not a problem
since we already
have a web site setup.
Personally I'd
On Wed, Sep 27, 2000 at 06:03:30PM -0400, George France wrote:
Please also read Mike Touloumtzis [[EMAIL PROTECTED]] posting in the
arm-linux-kernel archives. He gets the concept.
Maybe I do, but I thought I was agreeing with Russell :-). Which
only serves to underscore the silliness of
Yes you should be able to mix 16x50 chips with sa1100 chips. That is not the
issue. I believe that people can place any mixture of IC's on a PCB.
Letting it make sense is another issue. Placing a Z80 next to an AMD
Irongate doesn't make sense to me...
HPA can I suggest the description for
28 matches
Mail list logo
