This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Disable HAL comm channel?
- From: Grant Edwards <grante at visi dot com>
- To: Gary Thomas <gthomas at redhat dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: Fri, 19 Apr 2002 14:08:34 -0500
- Subject: Re: [ECOS] Disable HAL comm channel?
- References: <20020419130654.A28324@visi.com> <1019242412.24344.24.camel@hermes>
On Fri, Apr 19, 2002 at 12:53:30PM -0600, Gary Thomas wrote:
> > I've got a family of boards running RedBoot. For manufacturing
> > cost reasons, it's very desireable to run the exact same
> > bootloader image in all of the models. Some of the boards
> > have 3 diag channels, and some only have 2.
> >
> > Is there a way to disable a comm channel so that RedBoot won't
> > attempt to use it, or should I just fill in the function table
> > for that entry with stubs?
>
> I think you have three choices:
> 1) Disable RedBoot's use of any console - fix the console to
> a particular port.
> 2) Hard configure the number of I/O channels to the mininum
> common set, in your case two (hopefully they are proper
> subsets).
The product requirements dictate that all three ports work on
the boards that have them.
> 3) Add dummy/stubs entries for the unused channel when needed.
That's what I'll do. I thought maybe there was a simpler way
to disable a channel (though filling in the table with stubs
isn't very complicated).
Thanks.
--
Grant Edwards
grante@visi.com
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss