Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 17 Feb 2001 23:11:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 17 Feb 2001 23:11:45 -0500 Received: from site3.talontech.com ([208.179.68.88]:62762 "EHLO site3.talontech.com") by vger.kernel.org with ESMTP id ; Sat, 17 Feb 2001 23:11:34 -0500 Message-ID: <3A8F4C54.2010604@kalifornia.com> Date: Sat, 17 Feb 2001 20:15:16 -0800 From: Ben Ford User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.1 i586; en-US; 0.8) Gecko/20010215 X-Accept-Language: en MIME-Version: 1.0 To: jacob@chaos2.org CC: linux-kernel@vger.kernel.org Subject: Re: [LONG RANT] Re: Linux stifles innovation... In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jacob Luna Lundberg wrote: >> Speaking as a Linux _USER_, if this happens, can I get said print >> engine working on my ARM machines with these closed source drivers? >> Can Alpha users get this print system working? Can Sparc uses >> get it working? What? I can't? They can't? Well, its no good to >> me nor them. You've just made the system x86 specific. Well done, >> thats a step backwards, not forwards. > > > Just out of curiosity, why can't the specification be along the lines of a > vendor data file saying ``if you want the printer to do x then say y'' and > ``if the printer says x then it means y''. That ought to add a lot of > functionality right there. Sure there are evil winprinters that this > wouldn't be enough for but it would be hardware independant, yes? isn't that what windows *.INF files do? (don't flame me I'm not sure about it) -b - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/