From owner-freebsd-mobile Tue Jul 23 14:53:24 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB84D37B401 for ; Tue, 23 Jul 2002 14:53:20 -0700 (PDT) Received: from valemount.com (mailgate.valemount.com [209.53.76.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5DAF43E6E for ; Tue, 23 Jul 2002 14:53:18 -0700 (PDT) (envelope-from tony@valemount.com) Received: from tonyxp (forums.valemount.com) [209.53.76.17] by valemount.com [209.53.76.66] with SMTP (MDaemon.PRO.v5.0.7.R) for ; Tue, 23 Jul 2002 14:52:43 -0700 Message-ID: <104501c23293$64515bb0$114c35d1@tonyxp> From: "Tony Toole" To: Cc: "\"M. Warner Losh\"" References: <0f5001c23287$1a948530$114c35d1@tonyxp><20020723.150649.12657684.imp@bsdimp.com><100401c23290$cf2568d0$114c35d1@tonyxp> <20020723.153953.76074374.imp@bsdimp.com> Subject: Re: PCI -> PCMCIA Adapter woes - patch Date: Tue, 23 Jul 2002 14:53:34 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-MDRemoteIP: 209.53.76.17 X-Return-Path: tony@valemount.com X-MDaemon-Deliver-To: mobile@FreeBSD.ORG Reply-To: tony@valemount.com Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org That sounds quite reasonable. Linux pcmcia services may have an odd way of working their magic, but it does seem to work very well in any respect (as far as compatibility goes with various socket vendors). Given the information available, I think there is a chance to make a nice addition to FreeBSD's pcmcia socket compatibility if this code can be applied in a clean and safe manner. If anybody can do it, I'm sure you can. :) Thanks, Tony Toole ----- Original Message ----- From: "M. Warner Losh" To: Cc: ; Sent: Tuesday, July 23, 2002 2:39 PM Subject: Re: PCI -> PCMCIA Adapter woes - patch > In message: <100401c23290$cf2568d0$114c35d1@tonyxp> > "Tony Toole" writes: > : I don't have the docs you mentioned, however from reviewing various other > : pieces of information (such as the Linux PCMCIA implementation), this is > : needed. What harm would it do to a card that either doesn't support it > : (like the 11xx), or ones that already have it working such as (probably) > : Laptops? The cards we use are from Elan, however we have several smaller > : SBC units with integrated TI1211 chips that also require this workaround. > : Perhaps a reasonable thing to do is provide a sysctl to enable / disable the > : fix on bootup? > > The harm on laptops would be if they are wired in a weird way. The > harm for TI-113[01] parts would be that they might behave in unknown > or unpreditable ways if we did this. Sure, we could test it, but we > couldn't be sure. IIRC, the only way to get the PCI signals is to use > the mutlifunction pins to get them. I think it would be safest to do > the fixup iff it is 0 to start with AND the user doesn't say not to do > it. > > The Linux pcmica code isn't always as careful with these things as it > should be. There have been a number of occasions where > workarounds/hacks in that code are later revised because they were too > broadly applied in the initial version(s). So you have to be careful > how you take workarounds from that code base. > > I'll try to work up a better fix that I'd be more comfortable with and > post it later. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message