Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161980AbWLAVq0 (ORCPT ); Fri, 1 Dec 2006 16:46:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161994AbWLAVq0 (ORCPT ); Fri, 1 Dec 2006 16:46:26 -0500 Received: from foo.birdnet.se ([213.88.146.6]:58264 "EHLO foo.birdnet.se") by vger.kernel.org with ESMTP id S1161980AbWLAVqZ (ORCPT ); Fri, 1 Dec 2006 16:46:25 -0500 Message-ID: <20061201214631.6991.qmail@cdy.org> Date: Fri, 1 Dec 2006 22:46:31 +0100 From: Peter Stuge To: "Eric W. Biederman" Cc: Greg KH , Andi Kleen , Stefan Reinauer , linuxbios@linuxbios.org, linux-kernel@vger.kernel.org, "Lu, Yinghai" Subject: Re: [LinuxBIOS] #57: libusb host program for PLX NET20DC debug device Mail-Followup-To: "Eric W. Biederman" , Greg KH , Andi Kleen , Stefan Reinauer , linuxbios@linuxbios.org, linux-kernel@vger.kernel.org, "Lu, Yinghai" References: <5986589C150B2F49A46483AC44C7BCA4907276@ssvlexmb2.amd.com> <20061201191916.GB3539@suse.de> <20061201204249.28842.qmail@cdy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1711 Lines: 49 On Fri, Dec 01, 2006 at 02:15:24PM -0700, Eric W. Biederman wrote: > Right. For LinuxBIOS not a problem for earlyprintk in the kernel > somethings might need to be refactored. The challenge in the > kernel is we don't know at build to how to do a pci_read_config... > > The other hard part early in the kernel is the fact that the > bar is memory mapped I/O. Which means it will need to get mapped > into the kernels page tables. I see. > >> And I have some code that barely works for this already, perhaps > >> Eric and I should work together on this :) > > > > I would be interested in having a look at any code for it too. > > Sure, I will send it out shortly. I currently have a working > user space libusb thing (easy, but useful for my debug) Hm - for driving which end? > and a rude read/write to the bar from user space program that How does that work? /dev/{port,mem}? > allowed me to debug the worst of the state machine from user > space. I don't think I have the state setup logic correct yet > but that is minor in comparison. > > I really wish the EHCI spec had made that stupid interface 16 bytes > instead of 8 or had a way to chain multiple access together. The > we could have used a normal usb cable. As it is most descriptors > are 1 byte to big to read. Which descriptors are you reading? The debug port isn't really supposed to be used with anything but a debug device - which can't be enumerated normally anyway. //Peter - 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/