s
just the scenario I encountered is very similar: the serial interface
is flooded with breaks, after a while the prot generates an IRQ storm.
But the storm happens only after the port gets shut down (by getty in
my case).
In my case this behavior is due to a SW bug, you might be hitting the
HW
CRTSCTS)
uart_set_mctrl(port, TIOCM_RTS);
^^
I did not get to trying to submit it, but it sure gets rid o the storm.
cheers,
/vb
On Fri, Feb 26, 2010 at 11:25 AM, Paul Gortmaker
wrote:
> Sending a break on the SOC UARTs found in some
Guys, are there other instances of nested C functions in the codebase
or was this the first attempt?
On Wed, Oct 7, 2009 at 9:11 AM, Grant Likely wrote:
> On Wed, Oct 7, 2009 at 9:15 AM, Jérôme Pouiller wrote:
>> Dear,
>>
>> I have a problem with commit 8bc487d150b939e69830c39322df4ee486efe381
I'm debugging a fairly awkward system, where the ehernet controller
and the phy device connected to the controller's mac are completely
independent. (this is in the 2.6.25 tree, btw).
The phy device interface is through SysFs attributes, there is no
interrupts, link state is polled by a user space
