On Fri, Oct 24, 2014 at 2:16 PM, Daniel Gutson
wrote:
> On Fri, Oct 24, 2014 at 2:33 AM, Sebastian Huber
> wrote:
>> On 23/10/14 18:12, Daniel Gutson wrote:
>>>
>>> On Thu, Oct 23, 2014 at 5:47 AM, Sebastian Huber
>>> wrote:
>Hello Daniel,
>>>
>>> Hi Sebastian,
>>>
>
>I neve
On Fri, Oct 24, 2014 at 2:33 AM, Sebastian Huber
wrote:
> On 23/10/14 18:12, Daniel Gutson wrote:
>>
>> On Thu, Oct 23, 2014 at 5:47 AM, Sebastian Huber
>> wrote:
>>>
>>> >Hello Daniel,
>>
>> Hi Sebastian,
>>
>>> >
>>> >I never notice a problem with this driver. It should only write to the
>>>
On 23/10/14 18:12, Daniel Gutson wrote:
On Thu, Oct 23, 2014 at 5:47 AM, Sebastian Huber
wrote:
>Hello Daniel,
Hi Sebastian,
>
>I never notice a problem with this driver. It should only write to the FIFO
>in case it is completely empty. Did you observe problems?
no, I didn't (actually I
On Thu, Oct 23, 2014 at 5:47 AM, Sebastian Huber
wrote:
> Hello Daniel,
Hi Sebastian,
>
> I never notice a problem with this driver. It should only write to the FIFO
> in case it is completely empty. Did you observe problems?
no, I didn't (actually I found this while looking for a serial bug
Hello Daniel,
I never notice a problem with this driver. It should only write to the FIFO in
case it is completely empty. Did you observe problems?
On 21/10/14 19:32, Daniel Gutson wrote:
Hi,
in the writing interrupt mode (ns16550_write_support_int), we have
for (i = 0; i < out; ++
Hi,
in the writing interrupt mode (ns16550_write_support_int), we have
for (i = 0; i < out; ++i) {
set( port, NS16550_TRANSMIT_BUFFER, buf [i]);
}
Shouldn't we check, before writing to the register for the iterations
after the first one,
whether the character entered in the FIFO? (oth
