From owner-cvs-all Sun Jun 11 15: 2: 1 2000 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9A55F37B5ED; Sun, 11 Jun 2000 15:01:21 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id AAA02479; Mon, 12 Jun 2000 00:01:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/musycc musycc.c In-reply-to: Your message of "Sun, 11 Jun 2000 13:43:28 PDT." <200006112043.NAA15090@mass.cdrom.com> Date: Mon, 12 Jun 2000 00:01:19 +0200 Message-ID: <2477.960760879@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200006112043.NAA15090@mass.cdrom.com>, Mike Smith writes: >> phk 2000/06/11 12:09:48 PDT >> >> Added files: >> sys/dev/musycc musycc.c >> Log: >> The very feeble beginnings of a driver for the LanMedia LMC1504 card. >> >> New-Bus wizards are encouraged to look at this, I think it poses a >> challenge for the current newbus design. > >Can you be a little more explicit about the nature of the problem? It >looks pretty straightforward from here... > >Making some assumptions - function 0 and function 1 both describe >resources that a single driver instance requires in order to operate >correctly. Right with the added twist that identification doesn't complete until I have had a chance to poke at function 1. In other words, I can't really claim function 0 when I see it, because I don't know if it is part of the card I'm looking for or another card and I will not know until I get to probe function 1. The card looks like this: ############### func0 # / \ # / \ # | \ PCI ==# | | # Framer0 Framer1 [...] # | | # | | ### func1 ======= "ebus"=======-- ID-prom Your suggestions all sound like equally hackish ways to do it as what I have done in my code, and maybe we don't want to support this kind of hardware in any more respectable way than with some kind of hack ? For another problem of this class, look at the Znyx314 detection in if_de -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message