From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "q.kontinuum" Newsgroups: comp.lang.ada Subject: Re: Linux kernel module - memory allocation Date: Tue, 19 May 2015 09:56:54 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <8759d49e-c30a-4c71-a3e5-fd7a818a30f6@googlegroups.com> Reply-To: nntp@thorzten.de NNTP-Posting-Host: 2Re8NKytgV911fAPUMdAmQ.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org User-Agent: slrn/1.0.1 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:25918 Date: 2015-05-19T09:56:54+02:00 List-Id: On 2015-05-19, jan.de.kruyf@gmail.com wrote: > On Tuesday, May 19, 2015 at 7:30:37 AM UTC+2, q.kontinuum wrote: > >> I think I might be a different learning type. > > Age related I guess. > I was forced to take your way with an ethernet driver for an arm board since > no good example was available (at least not for what I wanted) And oh boy > was I bitten in the foot! But it is running now. Hehe :-) I wrote an ethernet-driver for a Z80 (don't ask...) ~14 years ago. I feel your pain. But that time I did read the specs, and much good did it to me. In the end I had to get a logic analyzer to check what was going on on the bus because the chip didn't abide the specs. >> I didn't find anything about this. Do you have some additional information? >> > > file:///usr/gnat/share/doc/gnat/html/gnat_rm_2.html#SEC6 (on my machine) Ok, I guess I should be able to find this somewhere. Although a quick google search did not show a relevant package. [...] >> As I wrote in another thread, it's a gcc feature. >> https://gcc.gnu.org/onlinedocs/gcc-4.5.3/gcc/i386-and-x86_002d64-Options.html >> > > Yes, i take it you did see my post about the > load of other switches the module building process inserts > into the call to gcc. Yes, although I didn't look into that much. I just looked up a short tutorial like "getting started", and took the parameters from there. Quite simple, actually. This is my current Makefile at the moment: https://github.com/thors/ada/blob/master/driver/Makefile Br, Thorsten