This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: hal_diag serial driver: using XON/XOFF flow control?


This is all totally unnecessary. If you want interrupt driven IO,
write a proper driver for it! Don't try and hack it into code that was
never intended to support it.

Actually, I don't really care about the interrupt driven IO. All I need is a serial connection that respects the flow control messages it's being sent. Because otherwise the debug messages I send will be corrupted.

Tell me then what's neccessary to set up a real serial driver. I see how to write it from the docs. But since I only have one serial port, I need to share it with the HAL serial driver. Is that feasible? What means of synchronization are neccessary? How will that work with remote gdb? While I'm writing I realize that it's probably not possible.

I admit, it's a lot of constraints. No hardware flow control, only one UART. Still, I have to work with it.

Heiko

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]