On Sat, 2010-06-19 at 00:47 +0800, wilbur.chan wrote:
> For example, a macro in serial driver 8250.c , SERIAL_PORT_DFNS ,I
> can't find where it is implement.
It looks to be in 8250.c, so I don't know why you can't find it.
> Is there any solutions to find a macro defination in code ?
# make tag
On 06/15/10 23:52, M. Warner Losh wrote:
> In message: <4c187013.5000...@firmworks.com>
> Mitch Bradley writes:
> : Mike Rapoport wrote:
> : > Mitch Bradley wrote:
> : >> Mike Rapoport wrote:
> : >>> Mitch Bradley wrote:
> : >>>
> : The second topic is the hypothetical use of OFW
On Fri, Jun 18, 2010 at 10:33:06AM +1000, Anton Blanchard wrote:
>
> If we configure with CONFIG_SMP=n or set NR_CPUS less than the number of
> SMT threads we will set the max cores property to 0 in the
> ibm,client-architecture-support structure. On new versions of firmware that
> understand this
2010/6/18 wilbur.chan :
> For example, a macro in serial driver 8250.c , SERIAL_PORT_DFNS ,I
> can't find where it is implement.
>
> Is there any solutions to find a macro defination in code ?
>
> Thx
Yes, use the lxr engine [1].
[1] http://lxr.linux.no
__
For example, a macro in serial driver 8250.c , SERIAL_PORT_DFNS ,I
can't find where it is implement.
Is there any solutions to find a macro defination in code ?
Thx
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/lis
On Thu, May 20, 2010 at 09:35:56PM +0200, Andre Prendel wrote:
> On Thu, May 20, 2010 at 03:07:05PM -0400, Jeff Angielski wrote:
> > On 05/20/2010 02:50 PM, Andre Prendel wrote:
> > > You made a careless mistake, see below. Please fix this and resend the
> > > patch
> > > again. Then I added my Ac
From: Chuck Meade
The UCC UART driver is missing a call to uart_update_timeout().
Without this call, attempting to close the port after outputting large
amounts of data (i.e. using tty and uart buffering) results in long
timeouts before the port will actually be shut down.
For example, cat a lar
On Sat, Jun 12, 2010 at 02:27:12PM +0800, Barry Song wrote:
> On Wed, Aug 19, 2009 at 5:46 AM, Anton Vorontsov
> wrote:
> >
> > Previosly the driver always tried JEDEC probing, assuming that non-JEDEC
> > chips will return '0'. But truly non-JEDEC chips (like CAT25) won't do
> > that, their behavi
