From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Brolley To: "Frank Ch. Eigler" Cc: sid@sources.redhat.com Subject: Re: Sid: Is there a bus selector component? Date: Thu, 29 Mar 2001 17:56:00 -0000 Message-id: <3AC35CEA.2070701@redhat.com> References: <3AC2771F.D0BE6829@redhat.com> <20010328191657.N11408@redhat.com> X-SW-Source: 2001-q1/msg00104.html After some thought, it looks like I could do this with two of the existing bus-bux components: connect-pin control selector -> mux1 switch connect-pin control selector -> mux2 switch connect-bus master1 bus mux1 upstream connect-bus master2 bus mux2 upstream connect-bus mux1 downstream1 slave read-write-port # don't connect mux1 downstream2 to anything # don't connect mux2 downstream1 to anything connect-bus mux2 downstream2 slave read-write-port Turns out that bux-mux returns sid::bus::unmapped if the selected accessor is not connected. Any objections if I punt on the new selector component and just do this? Dave Frank Ch. Eigler wrote: > Hi - > > On Wed, Mar 28, 2001 at 06:43:27PM -0500, Dave Brolley wrote: > : I have a need for the inverse of the hw-glue-bus-mux component. [...] > > Interesting - why? > > : Do we have anything like this? I'm not very familiar with the > : component library. > > Nope. It should not be hard to write one. > > - FChE