change log for rtems (2011-02-15)

[Joel Sherrill]

On 02/16/2011 08:49 AM, Sebastian Huber wrote:
> On 02/16/2011 03:35 PM, Joel Sherrill wrote:
>> On 02/16/2011 08:31 AM, Joel Sherrill wrote:
>>> On 02/16/2011 01:43 AM, Sebastian Huber wrote:
>>>> On 02/16/2011 01:10 AM, rtems-vc at rtems.org wrote:
>>>> [...]
>>>>> diff -u rtems/c/src/libchip/serial/ns16550_p.h:1.15
>>>>> rtems/c/src/libchip/serial/ns16550_p.h:1.16
>>>>> --- rtems/c/src/libchip/serial/ns16550_p.h:1.15    Fri Apr  9
>>>>> 17:44:05 2010
>>>>> +++ rtems/c/src/libchip/serial/ns16550_p.h    Tue Feb 15 17:25:24 2011
>>>>> @@ -27,7 +27,7 @@
>>>>>      *  will show up in the symbol table.
>>>>>      */
>>>>>
>>>>> -#define NS16550_STATIC static
>>>>> +#define NS16550_STATIC
>>>>>
>>>>>     #define NS16550_RECEIVE_BUFFER   0
>>>>>     #define NS16550_TRANSMIT_BUFFER  0
>>>> [...]
>>>>
>>>> What is the cause for this?
>>>>
>>> So you can use the libchip support for printk.
>>>
>>> There is a replacement driver for the pc386 coming.
>>>
>>>
>> I should have mentioned that Jennifer wants to
>> try to find a way to more generally provide
>> printk support for libchip style drivers.
> The general way is to access static functions?
>
>>
>> FWIW the replacement driver for pc386 is
>> libchip style so it can support more than
>> 2 com ports.  I am close to committing
>> part of the work which moves serial mouse
>> shared support into cpukit.  This includes
>> a BSP independent serial mouse driver
>> and the mouse_parser code.
> Please think also about how an application can access such a driver:
>
> http://www.rtems.org/pipermail/rtems-users/2010-December/007794.html
>
> I think there is no need to introduce a RTEMS specific API here.
>
I don't think that is in conflict with anything
I am doing.  This is mostly a clean up of existing
code which supported Microwindows to make it BSP
independent.  The mouse parser code takes input,
decodes it, and puts it in a uniform message independent
of mouse type.  The code in libmisc/fb should have
been more involved.  The serial driver is now completely
unaware of the Microwindows ioctl's.

Do you have a bundle of those .h files?  I think they
will help with porting svgalib.

If we need to add more functionality, then this
should make it easier.  A serial driver should not be
Microwindows aware.

-- 
Joel Sherrill, Ph.D.             Director of Research&  Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
    Support Available             (256) 722-9985