change log for rtems (2010-04-30)

[Sebastian Huber]

On 05/01/2010 02:01 AM, Chris Johns wrote:
> On 30/04/2010 7:12 PM, rtems-vc at rtems.org wrote:
>>   /**
>> + * @brief See _Chain_Get_unprotected().
>> + */
>> +RTEMS_INLINE_ROUTINE rtems_chain_node *rtems_chain_get_unprotected(
>> +  rtems_chain_control *the_chain
>> +)
>> +{
>> +  return _Chain_Get_unprotected( the_chain );
>> +}
>> +
>> +/**
>>    *  @brief Insert a node on a chain
>>    *
>>    *  This routine inserts @a the_node on a chain immediately following
>> @@ -402,6 +412,17 @@
>>   }
>>
>>   /**
>> + * @brief See _Chain_Insert_unprotected().
>> + */
>> +RTEMS_INLINE_ROUTINE void rtems_chain_insert_unprotected(
>> +  rtems_chain_node *after_node,
>> +  rtems_chain_node *the_node
>> +)
>> +{
>> +  _Chain_Insert_unprotected( after_node, the_node );
>> +}
>> +
>> +/**
>>    *  @brief Append a node on the end of a chain
>>    *
>>    *  This routine appends @a the_node onto the end of @a the_chain.
>>
> 
> This will need an update to the documentation. I am not sure I have keep
> it updated. I will take a look and add these and anything else.

Thanks.

> 
>> +
>> +#include<rtems.h>
>> +#include<rtems/bdpart.h>
>> +#include<rtems/dosfs.h>
>> +#include<rtems/fsmount.h>
>> +
>> +rtems_status_code rtems_bdpart_mount(
>> +  const char *disk_name,
>> +  const rtems_bdpart_partition *pt __attribute__((unused)),
>> +  size_t count,
>> +  const char *mount_base
>> +)
> 
> What is required to add RFS support ?
> 
> I suppose it would need a partition id. I am not sure how these are
> allocated.

There is no official place to allocate a partition identifier.  See also

http://www.rtems.org/onlinedocs/doxygen/cpukit/html/group__rtems__bdpart.html#_details

http://www.win.tue.nl/~aeb/partitions/partition_types-1.html

-- 
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.