From: Adam Agnew <agnew@missl.cs.umd.edu>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: "Trenton D. Adams" <tadams@extremeeng.com>,
"'Matthew M. DeLoera'" <code.bear@gte.net>,
<ecos-discuss@sources.redhat.com>, <waa@cs.umd.edu>,
<bdpayne@cs.umd.edu>, <usn01a@wam.umd.edu>
Subject: Re: [ECOS] Problems with RedBoot on x86 generic pc...
Date: Fri, 14 Sep 2001 09:14:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.33.0109141221400.65789-100000@www.missl.cs.umd.edu> (raw)
In-Reply-To: <3BA0E06D.F904DF1A@redhat.com>
I finally found time to try that, and yes it worked on machines where it
wasn't working when there were two serial ports specified. Thanks, and I
hope this info is helpfull in tracking the bug down.
- adam agnewx
On Thu, 13 Sep 2001, Jonathan Larmour wrote:
> Adam Agnew wrote:
> >
> > I've tried the provided image for a floppy on several x86 boxen, and it
> > works on some, doesn't on others. As a test, i tried setting
> >
> > cdl_option CYGNUM_HAL_VIRTUAL_VECTOR_COMM_CHANNELS { user_value 1 };
> > and
> > cdl_option CYGSEM_HAL_I386_PC_DIAG_SCREEN { user_value 0 };
> >
> > That certainly cleared up the problem, but of course gets rid of the PC's
> > screen, which was nice. Maybe someone can use this info to track down the
> > bug, I'm not that familiar with the code base yet. But that's a temporary
> > fix for poor folks like me who it wasn't working for. Perhaps this is
> > just a problem with motherboards with only one serial port. Perhaps its
> > deeper, *shrug*.
>
> One way to find out if there's a problem with boards with one serial
> port.... go to hal/i386/pcmb/current/src/pcmb_serial.c and comment out the
> stuff for channel 1 in cyg_hal_plf_serial_init.
>
> Then go to pcmb_screen.c and in cyg_hal_plf_screen_init change all the "2"s
> to "1"s.
>
> Go to /hal_diag.c and remove the middle entry of pc_ser_channels and change
> the 3 to a 2.
>
> Finally go to hal/i386/pc/current/cdl_hal_i386_pc.cdl and change
> CYGNUM_HAL_VIRTUAL_VECTOR_COMM_CHANNELS to have:
>
> default_value { CYGSEM_HAL_I386_PC_DIAG_SCREEN ? 2 : 1 }
>
> Then build and try a redboot on a PC with one serial port. If it works
> where the old image didn't, let us know.
>
> Jifl
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
>
next prev parent reply other threads:[~2001-09-14 9:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 12:07 Matthew M. DeLoera
2001-07-11 14:25 ` Jonathan Larmour
2001-07-31 7:59 ` Trenton D. Adams
2001-07-31 10:56 ` Jonathan Larmour
2001-07-31 12:01 ` Trenton D. Adams
2001-07-31 13:43 ` Jonathan Larmour
2001-07-31 14:20 ` Trenton D. Adams
2001-07-31 14:23 ` Jonathan Larmour
2001-09-07 11:25 ` Adam Agnew
2001-09-13 2:02 ` Adam Agnew
2001-09-13 3:56 ` [ECOS] RedBoot IDE access on x86 without BIOS Adam Agnew
2001-09-13 4:51 ` Mark Salter
2001-09-13 6:18 ` Adam Agnew
2001-09-13 6:24 ` Mark Salter
2001-09-13 6:53 ` Adam Agnew
2001-09-13 9:36 ` [ECOS] Problems with RedBoot on x86 generic pc Jonathan Larmour
2001-09-14 9:14 ` Adam Agnew [this message]
2001-09-14 12:43 ` Matthew DeLoera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.4.33.0109141221400.65789-100000@www.missl.cs.umd.edu \
--to=agnew@missl.cs.umd.edu \
--cc=bdpayne@cs.umd.edu \
--cc=code.bear@gte.net \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
--cc=tadams@extremeeng.com \
--cc=usn01a@wam.umd.edu \
--cc=waa@cs.umd.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).