public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alex Lennon" <ajlennon@arcom.co.uk>
To: "Gary Thomas" <gthomas@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Re: Romboot in i386 (continued) - comms. problems
Date: Mon, 13 Aug 2001 04:23:00 -0000	[thread overview]
Message-ID: <NEBBKJHOALKOLCFPGELECEMLCPAA.ajlennon@arcom.co.uk> (raw)
In-Reply-To: <XFMail.20010813051056.gthomas@redhat.com>

>>Try looking in the file ".../hal/i386/pcmb/current/src/pcmb_serial.c"
>>You'll see that the FIFOs are explicitly *not* turned on.  You
>>can experiment
>>with that code a bit and see what works for you.
>>

Yes - that's what I've been referring to. Apologies for my lack of clarity.

What I was trying to say was that the FIFOs are not enabled in the
following code snippet (from pcmb_serial.c)

static void
cyg_hal_plf_serial_init_channel(void* __ch_data)
{
    cyg_uint16 base = ((channel_data_t*)__ch_data)->base;

    HAL_WRITE_UINT8(base+CYG_DEV_IER, 0);
    HAL_WRITE_UINT8(base+CYG_DEV_IER, 0);
    HAL_WRITE_UINT8(base+CYG_DEV_MCR, 0);

    HAL_WRITE_UINT8(base+CYG_DEV_LCR, SIO_LCR_DLAB);
    HAL_WRITE_UINT8(base+CYG_DEV_DLL, CYG_DEVICE_SERIAL_BAUD_LSB);
    HAL_WRITE_UINT8(base+CYG_DEV_DLM, CYG_DEVICE_SERIAL_BAUD_MSB);
    // 8-1-no parity.
    HAL_WRITE_UINT8(base+CYG_DEV_LCR, SIO_LCR_WLS0 | SIO_LCR_WLS1);

//    HAL_WRITE_UINT8(base+CYG_DEV_FCR, 0x07);  // Enable & clear FIFO
}

They aren't *disabled* either - so the FIFOs aren't necessarily disabled.
Only an issue
if you have a couple of different loader programs chaining each other as we
do here.

I take your point that I can enable the FIFOs and add code to the handler to
deal with this.
However, to support FIFOs I need to buffer up the incoming characters on
each
cyg_hal_plf_serial_getc_nonblock() call.

I'm happy enough to do this but I'd prefer to just reuse the existing eCos
16x5x code
rather than putting something new together. I just wondered if this was
likely to prove
a problem ? Particularly if there is something difficult about the i386
protected mode
setup of which I am unaware...

Regards,

 Alex




_____________________________________________________________________
This message has been checked for all known viruses by UUNET delivered 
through the MessageLabs Virus Control Centre. For further information visit
http://www.uk.uu.net/products/security/virus/

  reply	other threads:[~2001-08-13  4:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  3:21 Alex Lennon
2001-08-13  3:39 ` Gary Thomas
2001-08-13  3:52   ` Alex Lennon
2001-08-13  4:11     ` Gary Thomas
2001-08-13  4:23       ` Alex Lennon [this message]
2001-08-13 10:45         ` Jonathan Larmour
2001-08-14  5:06           ` Alex Lennon
2001-08-14  5:32             ` Jonathan Larmour
2001-08-13  4:30     ` Nick Garnett
2001-08-13  4:30   ` Nick Garnett

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=NEBBKJHOALKOLCFPGELECEMLCPAA.ajlennon@arcom.co.uk \
    --to=ajlennon@arcom.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gthomas@redhat.com \
    /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).