From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kurt Van Dijck Subject: Re: [RFC v3 5/6] j1939: rename NAME to UUID? Date: Sat, 23 Apr 2011 07:51:09 +0200 Message-ID: <20110423055109.GC330@kurt.e-circ.dyndns.org> References: <20110314132004.GA333@e-circ.dyndns.org> <20110314135917.GF333@e-circ.dyndns.org> <4D8623BE.2080807@hartkopp.net> <20110413044928.GA289@kurt.e-circ.dyndns.org> <4DA88705.5040203@hartkopp.net> <20110420072439.GB332@kurt.e-circ.dyndns.org> <20110422141832.GB334@kurt.e-circ.dyndns.org> <4DB19B46.4000306@hartkopp.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Oliver Hartkopp Return-path: Content-Disposition: inline In-Reply-To: <4DB19B46.4000306-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: socketcan-core-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org Errors-To: socketcan-core-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org List-Id: netdev.vger.kernel.org On Fri, Apr 22, 2011 at 05:14:14PM +0200, Oliver Hartkopp wrote: > On 22.04.2011 16:18, Kurt Van Dijck wrote: > > On Wed, Apr 20, 2011 at 09:24:39AM +0200, Kurt Van Dijck wrote: > >> I need to git pull the latest updates, and I'll send a revised patchset > >> tomorrow. > > Oliver, > > > > I did not forget, but something came in between. next week for sure. > > Oh, no problem. > > I'm constantly working on my reply to your latest answer 8-) > > BTW: Do you have any sample code that shows, how the sending (and receiving) > of the same BAM message would look like in the static and in the > address-claimed case?? I'm not really able to extract this information from > your posted documentation. > > I would like to know > > - what has to be configured before (from the user and the admin) > - how does the application source code look like in the requested four cases > > I think we're a bit stuck in the discussion of the 'easy to use' socket API > without having real-world examples. ack. Since I think I got the stack stable now (and some LOC dropped), I agree that 'simple' real-world examples may document a lot. > > Thanks, > Oliver Kurt