From: "Dave Airlie" <airlied@parthus.com>
To: "Jesper Skov" <jskov@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] serial compilation with CYGINT_IO_SERIAL_BLOCK_TRANSFER
Date: Wed, 13 Sep 2000 04:45:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0009131251270.8040-100000@platinum.limerick.sslinc.com> (raw)
In-Reply-To: <otvgw0sfw2.fsf@thinktwice.zoftcorp.dk>
But I have another driver that does implement the interfaces, and I need
to run it and the PID serial ports,
Can I not do this?
Dave.
On 13 Sep 2000, Jesper Skov wrote:
> >>>>> "Dave" == Dave Airlie <airlied@parthus.com> writes:
>
> Dave> Hi, I've just gotten the snapshot from the 8th Sept, and cannot
> Dave> get the serial stuff to compile with
> Dave> CYGINT_IO_SERIAL_BLOCK_TRANSFER enabled..
>
> Dave> in serial.c it keeps getting problems in the differing
> Dave> SERIAL_CALLBACKS...
>
> Dave> Has anyone else had problems like this .. I'm running an ARM-PID
> Dave> board
>
> That is an interface, not a user-modifyable option. If the _driver_
> does not implement block transfers (which the PID driver does not),
> the interface will not be activated.
>
> The callback compile errors are due to the IO driver expecting the
> callbacks functions to be defined by the device driver - and they
> are not.
>
> Jesper
>
--
David Airlie, Software Engineer, Parthus Technologies plc.,
Mary Rosse Centre, National Tech Park, Limerick, Ireland.
t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com
next prev parent reply other threads:[~2000-09-13 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 3:22 Dave Airlie
2000-09-13 4:14 ` Jesper Skov
2000-09-13 4:45 ` Dave Airlie [this message]
2000-09-13 4:52 ` Jesper Skov
2000-09-13 6:17 ` Dave Airlie
2000-09-13 6:34 ` Jesper Skov
2000-09-13 6:37 ` Dave Airlie
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.LNX.4.21.0009131251270.8040-100000@platinum.limerick.sslinc.com \
--to=airlied@parthus.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jskov@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).