Re: 16650

1997-04-23 Thread Adrian Phillips
 Steve == Steve Hsieh [EMAIL PROTECTED] writes:

  I'm certainly interested because I intend to be getting a
 byte runner 16650  card and ISDN TA in a about a week.


Steve Something to think about before getting a 16650
Steve card... From the 2.0.30 kernel serial.c:

patch for problem with 16550 chip clipped

I think that most 16550 cards sold today (and fitted to most machines
are the 16550A - if you notice the rest of the code around that patch
you'll see that there is a test for 16550A first then 16550 (if I
remember what I've read a while ago rightly the 16550 was a bodged
version - then 16550A was released which fixed the problem),

Adrian


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: 16650

1997-04-23 Thread Steve Hsieh

I was refering to the 16650 (not 16550)... :-)
^

On 23 Apr 1997, Adrian Phillips wrote:

  Steve == Steve Hsieh [EMAIL PROTECTED] writes:
 
   I'm certainly interested because I intend to be getting a
  byte runner 16650  card and ISDN TA in a about a week.
 
 
 Steve Something to think about before getting a 16650
 Steve card... From the 2.0.30 kernel serial.c:
 
 patch for problem with 16550 chip clipped
 
 I think that most 16550 cards sold today (and fitted to most machines
 are the 16550A - if you notice the rest of the code around that patch
 you'll see that there is a test for 16550A first then 16550 (if I
 remember what I've read a while ago rightly the 16550 was a bodged
 version - then 16550A was released which fixed the problem),




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: 16650 - Found a patch!

1997-04-23 Thread Dave Cinege
On Wed, 23 Apr 1997 03:24:11 -0400 (EDT), Steve Hsieh wrote:


   I'm certainly interested because I intend to be getting a byte runner 
 16650 
   card and ISDN TA in a about a week.


Something to think about before getting a 16650 card... From the 2.0.30
kernel serial.c:

Hmm this is not good, but looky what I found:

serial .c
 * 16650/16750 support added for Connect Tech Inc ( www.connecttech.com )
 * DFlex support. For now, only fifos are enabled. Extra features of these
 * chips will be dealt with at a later date.

I checked out the DFlex, and it is more along the lines of an industrial 
board and carries a big price tag.

Now this should allow 16650 support on any board since the DFlex is dumb. 

Question: Where does the licensing for this patch stand? It is based 
on the standard serial.c from the kernal tree, which means this must also be
GPL, correct?




Dave 'Kill a Cop' Cinege  (aka Psychopath #3)  ---  Super Genius at Large
The Oklahoma City Federal building bombing - 
Americas first response to government abuse 

http://www.psychosis.com/

Libertarian Party 1-800-682-1776http://www.lp.org/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: 16650

1997-04-23 Thread Bob Nielsen
But they are enabled for 16550A, which is the only type you will find
these days.

Bob

On Wed, 23 Apr 1997, Steve Hsieh wrote:

 
I'm certainly interested because I intend to be getting a byte runner 
  16650 
card and ISDN TA in a about a week.
 
 
 Something to think about before getting a 16650 card... From the 2.0.30
 kernel serial.c:
 
 } else if (info-type == PORT_16650) {
 /*
  * On the 16650, we disable the FIFOs altogether
  * because of a design bug in how the implement
  * things.  We could support it by completely changing
  * how we handle the interrupt driver, but not today
  *
  * N.B.  Because there's no way to set a FIFO trigger
  * at 1 char, we'd probably disable at speed below
  * 2400 baud anyway...
  */
 fcr = 0;
 
 
 
 --
 TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
 [EMAIL PROTECTED] . 
 Trouble?  e-mail to [EMAIL PROTECTED] .
 
 
 


Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ  AMPRnet:  [EMAIL PROTECTED]
AX.25:[EMAIL PROTECTED]
http://www.primenet.com/~nielsen


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: 16650

1997-04-23 Thread Oleg Krivosheev


Hi there

if my memory still serves me, 16650 was issued with
bug in FIFO handling, so you can easily loose
bytes. After some time bug was fixed and now
good 16650 are in production. Unfortunately, there is
no way to find out chip info, i.e. there is no
difference between good 16650 and buggy one.

Try to ask Theodore Tso, who is maintaining
linux serial drivers.

cheers

OK

On Wed, 23 Apr 1997, Bob Nielsen wrote:

 But they are enabled for 16550A, which is the only type you will find
 these days.
 
 Bob
 
 On Wed, 23 Apr 1997, Steve Hsieh wrote:
 
  
 I'm certainly interested because I intend to be getting a byte runner 
   16650 
 card and ISDN TA in a about a week.
  
  
  Something to think about before getting a 16650 card... From the 2.0.30
  kernel serial.c:
  
  } else if (info-type == PORT_16650) {
  /*
   * On the 16650, we disable the FIFOs altogether
   * because of a design bug in how the implement
   * things.  We could support it by completely changing
   * how we handle the interrupt driver, but not today
   *
   * N.B.  Because there's no way to set a FIFO trigger
   * at 1 char, we'd probably disable at speed below
   * 2400 baud anyway...
   */
  fcr = 0;
  
  
  
  --
  TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
  [EMAIL PROTECTED] . 
  Trouble?  e-mail to [EMAIL PROTECTED] .
  
  
  
 
 
 Bob Nielsen Internet: [EMAIL PROTECTED]
 Tucson, AZ  AMPRnet:  [EMAIL PROTECTED]
 AX.25:[EMAIL PROTECTED]
 http://www.primenet.com/~nielsen
 
 
 --
 TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
 [EMAIL PROTECTED] . 
 Trouble?  e-mail to [EMAIL PROTECTED] .
 
 

 Oleg Krivosheev, 
 MS 345, AD/Physics,
 Fermi National Accelerator Laboratory,
 P.O.Box 500, Batavia, Illinois, 60510.
 phone: (630) 840 8460
 FAX  : (630) 840 4552
 Email: [EMAIL PROTECTED]


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .