From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 12 13:21:05 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B3A9A106566B for ; Thu, 12 Jul 2012 13:21:05 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 644C68FC12 for ; Thu, 12 Jul 2012 13:21:05 +0000 (UTC) Received: by yhfs35 with SMTP id s35so2969296yhf.13 for ; Thu, 12 Jul 2012 06:21:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=Bg654VVqjMWN+VjKSmVNGjVxSOY4jJKrne9NDuPlQ/Y=; b=H0aFlvYadDs+2aWBzllYVc3QdaHpUSkh+QCi3P5TKELR5DjacfT/Aq3VasaeFpyB7H +mMYPx/4ZgHpRD63KtBuWMi8DtBNNNw5UFyXQbc2M5WMA5jPlQ4ssAA6gIg+yH+kHCor IoUTLUwr10FVvOYf28JkyFZ0lCMRKV3vuoImD/R1jSV8JRsW4hFBn79qryRNoKsqcZRQ iE+Ga0mAMJtU6iPTGP84fLsDgyljYZqOwb/aYLBrmIWUz0+TlI+f+wGasBNWuqwNMXcN bwBX9YMN1ubIJE1gxV6rAaOIv7fip6aonIJWV66CR2Ofaw5Ni1i98Hcpku5TXJwGPPH/ TOGg== Received: by 10.68.227.198 with SMTP id sc6mr5423759pbc.138.1342099262621; Thu, 12 Jul 2012 06:21:02 -0700 (PDT) Received: from [10.0.0.63] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id gh9sm3865763pbc.20.2012.07.12.06.21.00 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Jul 2012 06:21:01 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <201207120801.25810.jhb@freebsd.org> Date: Thu, 12 Jul 2012 07:20:59 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <40098958-831C-49AE-8A7A-BE0B8EE15C34@bsdimp.com> References: <73F3FBC9-337C-4F61-9470-5173D6DAE56B@bsdimp.com> <201207120801.25810.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQlg0PS38WoZ9HYyh9RhjxQiEqQgbgr9f5VnYGQhlbPIIHcEEWFZVeVhNBkWNcjSmaMHYtbf Cc: FreeBSD Hackers , freebsd-current@freebsd.org, Arnaud Lacombe Subject: Re: newbus' ivar's limitation.. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2012 13:21:05 -0000 On Jul 12, 2012, at 6:01 AM, John Baldwin wrote: > New-bus is certainly not the only way to organize a device hierarchy = and is=20 > not perfect, but in your case I suggest you tone down your language = until you=20 > have enough information to develop an informed opinion. It is also not the only way to represent relationships between objects, = or to export services to the rest of the kernel. =46rom earlier = descriptions, it seems like some of these relationships aren't very = newbus-y. =46rom what I know about FDT, many of them are 'this device's = interrupt pin is tied to GPIO 12 on controller 3' which isn't a = parent/child relationship, but rather some kind of interrupt cookie = you'll need to implement bus_setup_intr. Warner