Date: Fri, 05 Jun 1998 11:07:12 -0700 From: Julian Elischer <julian@whistle.com> To: hackers@FreeBSD.ORG, bde@FreeBSD.ORG Subject: For BDE: ALi retapes chip for FreeBSD! Message-ID: <357833D0.63DECDAD@whistle.com>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------500F9F3013728473695678E2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Moved up from -questions ..
too important!
One for bruce,
but maybe we could get a translation first?
This represents the first time I know of that a chip vendor is retaping
a chip to work correctly with FreeBSD..
--------------500F9F3013728473695678E2
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Return-Path: <owner-freebsd-questions@freebsd.org>
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id FAA29918
for <julian@alpo.whistle.com>; Fri, 5 Jun 1998 05:10:35 -0700 (PDT)
Received: from whistle.whistle.com(207.76.205.131), claiming to be "whistle.com"
via SMTP by alpo.whistle.com, id smtpd029915; Fri Jun 5 12:10:34 1998
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id FAA26879 for <julian@whistle.com>; Fri, 5 Jun 1998 05:10:30 -0700 (PDT)
Received: from gatekeeper.whistle.com(207.76.204.2) by whistle.com via smap (V1.3)
id sma026875; Fri Jun 5 05:10:02 1998
Received: (from smap@localhost) by gatekeeper.whistle.com (8.7.5/8.6.12) id FAA15120 for <julian@whistle.com>; Fri, 5 Jun 1998 05:10:02 -0700 (PDT)
Received: from ns3.harborcom.net( 206.158.4.14) by gatekeeper via smap (V2.0)
id xma015116; Fri, 5 Jun 98 05:10:01 -0700
Received: from hub.freebsd.org [204.216.27.18]
by ns3.harborcom.net with esmtp (Exim 1.82 #1)
id 0yhvJm-0003Gq-00; Fri, 5 Jun 1998 08:09:58 -0400
Received: from localhost (daemon@localhost)
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA01741;
Fri, 5 Jun 1998 04:33:11 -0700 (PDT)
(envelope-from owner-freebsd-questions)
Received: by hub.freebsd.org (bulk_mailer v1.6); Fri, 5 Jun 1998 04:33:01 -0700
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA01629
for freebsd-questions-outgoing; Fri, 5 Jun 1998 04:33:00 -0700 (PDT)
(envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from ali.com.tw (root@ali.ali.com.tw [210.67.80.34])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01615
for <freebsd-questions@FreeBSD.ORG>; Fri, 5 Jun 1998 04:32:40 -0700 (PDT)
(envelope-from syhsieh@ali.com.tw)
Received: from ali.com.tw (root@market.ali.com.tw [210.67.80.36]) by ali.com.tw (8.7.3/8.7.3) with ESMTP id TAA10469; Fri, 5 Jun 1998 19:48:22 +0800
Message-ID: <3577D9F3.80754AD7@ali.com.tw>
Date: Fri, 05 Jun 1998 19:43:47 +0800
From: Shiaw Yi Hsieh <syhsieh@ali.com.tw>
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: freebsd-questions@freebsd.org, johnson@ali.com.tw
Subject: FreeBSD 2.2.5 AND 2.2.6 can not found serial port at Acer labs. M5135
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.ORG
Dear sir,
Several month ago, one of our customers name Iwill feedback one
question:
FreeBSD 2.2.5 can not found UART port at Iwill motherboard (use Acer
labs. M5135). This parts is use Intel new technology name--serial IRQ.
and did not found any problem in the other parts such as M5113,M5123 AND
M1543.
And our R&D people made much effort to study how FreeBSD can not found
UART and Tape out a new version to fixed this issue(for 2.2.5).
But after we get the new chip we still have got the following issue:
1. FreeBSD boot from CD-ROM PASS
2. FreeBSD boot from HDD PASS
3 FreeBSD boot from FDD FAIL
After we studied the different between boot from CD-ROM,HDD AND FDD
we found the different is in the command and command recovery time when
FreeBSD polling UART's IRQ(read IIR register 2fa,3fa,2ea,3ea). The
recovery time of CD-ROM,HDD is around several us but FDD command
recovery time only 2us. would it possible last the FDD commend recovery
time to over 10us?
Maybe Serial IRQ will take more time when set IIR register and read 8259
to get the status, so we recommend OS polling or read those IIR register
it is better to last the recovery time to get the 8259 IRQ status.
Another issue is read 8259 IRQ status method, in the parallel IRQ you
can read from edge or level but NEW serial IRQ our chip M5135 only have
got a pulse and not the level. Maybe this is why FreeBSD can not found
UART.
Our new chip had been option to change the IRQ from pulse to level, but
in FDD boot still have this issue. Do you have any comments? And FreeBSD
test have been put in our chip verify item, so if you release new
version, please mail to us for testting.
If you have any comments please contact me: johnson@ali.com.tw
Thanks
JOHNSON CHEN / MANAGER Acer Labs. Inc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
--------------500F9F3013728473695678E2--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?357833D0.63DECDAD>