Re: wortel.h patch

[Bas Wijnen]

Hi,

For some reason, my signature was broken.  I looked into it, and think 
it's a bug in the list server.  To verify the signature, please change

Content-Type: multipart/mixed; 
boundary="------------010604020707020408010202"

to

Content-Type: multipart/mixed;
 boundary="------------010604020707020408010202"

(the version I sent had it on two lines, the one I received back from 
the list had them on one line).

Thanks,
Bas

Bas Wijnen wrote:
> Hi,
>
> Here's a small patch to change grants to maps in wortel.h.  I guess this 
> was overlooked when wortel.c was changed to do mapping instead of 
> granting.  I have used this some time ago, and it worked back then.  As 
> these items are only used for receiving memory, I can't imagine it 
> making a difference anyway, as long as there is no type checking for 
> this in L4 (and appearantly there isn't, otherwise it wouldn't have 
> worked without this patch).
>
> As a side note: can hurd-l4 bugs also be reported through savannah, or 
> is that only meant for the mach port?
>
> I also noticed that I had some spelling corrections of 
> libhurd-cap-server/README in my tree, I'm attaching a patch with those 
> as well.
>
> Thanks,
> Bas
>
> 2005-01-08  Bas Wijnen  <address@hidden>
>
>     * wortel.h (wortel_get_mem): Change grant_items to map_items to
>     match their use.
>
>
> ------------------------------------------------------------------------
>
> Index: wortel.h
> ===================================================================
> RCS file: /cvsroot/hurd/hurd-l4/wortel/wortel.h,v
> retrieving revision 1.15
> diff -u -p -r1.15 wortel.h
> --- wortel.h    1 Nov 2004 16:06:50 -0000       1.15
> +++ wortel.h    8 Jan 2005 21:06:46 -0000
> @@ -235,7 +235,7 @@ wortel_get_mem (void)
>  {
>    l4_msg_tag_t tag;
>    l4_word_t mrs[2];
> -  l4_grant_item_t grant_item;
> +  l4_map_item_t map_item;
>    
>    l4_accept (l4_map_grant_items (L4_COMPLETE_ADDRESS_SPACE));
>  
> @@ -246,9 +246,9 @@ wortel_get_mem (void)
>  
>    l4_store_mr (1, &mrs[0]);
>    l4_store_mr (2, &mrs[1]);
> -  grant_item = *((l4_grant_item_t *) mrs);
> +  map_item = *((l4_map_item_t *) mrs);
>  
> -  return l4_grant_item_snd_fpage (grant_item);
> +  return l4_map_item_snd_fpage (map_item);
>  }
>  
>  
>
>
> ------------------------------------------------------------------------
>
> Index: README
> ===================================================================
> RCS file: /cvsroot/hurd/hurd-l4/libhurd-cap-server/README,v
> retrieving revision 1.5
> diff -u -p -r1.5 README
> --- README      8 Apr 2004 00:40:38 -0000       1.5
> +++ README      8 Jan 2005 21:20:04 -0000
> @@ -20,7 +20,7 @@ An introduction to the capability system
>  
>  A server provides services to its clients.  In a capability system the
>  right to access a given service is called a capability.  This right is
> -hold by a client.  It was previously granted to the client by the
> +held by a client.  It was previously granted to the client by the
>  server.  The client can then make use of this right, cease it, or
>  transfer (copy) it to a new client.
>  
> @@ -123,7 +123,7 @@ Capability Classes
>  ------------------
>  
>  Capability classes require a capability object definition (via storage
> -size and constructor/desctructor callbacks), and a demuxer for
> +size and constructor/destructor callbacks), and a demuxer for
>  incoming RPC messages on capability objects from this class.
>  
>  After creating a class, you will usually want to start a manager
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> L4-hurd mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/l4-hurd

--
I encourage people to send encrypted e-mail (see http://www.gnupg.org).
If you have problems reading my e-mail, use a better reader.
Please send the central message of e-mails as plain text
   in the message body, not as HTML and definitely not as MS Word.
Please do not use the MS Word format for attachments either.
For more information, see http://129.125.47.90/e-mail.html

signature.asc
Description: OpenPGP digital signature