All of lore.kernel.org
 help / color / mirror / Atom feed
* Writing Linux Device drivers with NASM
@ 2006-03-13 15:45 ALberto Andres
  2006-03-13 16:56 ` Frank Kotler
  0 siblings, 1 reply; 3+ messages in thread
From: ALberto Andres @ 2006-03-13 15:45 UTC (permalink / raw)
  To: linux-assembly

Hi everybody, I'm writing a guide about device drivers in assembly under 
linux. I'm using NASM.  If anybody is interested here is the URL:

http://albertoandreotti.5000megs.com/

Bye!!

_________________________________________________________________
Un amor, una aventura, compañía para un viaje. Regístrate gratis en MSN Amor 
& Amistad. http://match.msn.es/match/mt.cfm?pg=channel&tcid=162349


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Writing Linux Device drivers with NASM
  2006-03-13 15:45 Writing Linux Device drivers with NASM ALberto Andres
@ 2006-03-13 16:56 ` Frank Kotler
  2006-03-13 17:38   ` ALberto Andres
  0 siblings, 1 reply; 3+ messages in thread
From: Frank Kotler @ 2006-03-13 16:56 UTC (permalink / raw)
  To: ALberto Andres; +Cc: linux-assembly

ALberto Andres wrote:
> Hi everybody, I'm writing a guide about device drivers in assembly under 
> linux. I'm using NASM.  If anybody is interested here is the URL:
> 
> http://albertoandreotti.5000megs.com/

Great, Alberto! Couple thing seems strange to me. I don't know anything 
about device drivers, so perhaps it really *is* that strange...

You say:

    2.      Stack cleanup is performed by the called function.
    3.      Function name is decorated by prepending an underscore character

But that doesn't seem to be what you show...

And... your strings have got CRs in 'em. Is that normal/required for 
device drivers?

I'm sure I'll have more questions... Great resource. Thanks!

Best,
Frank


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Writing Linux Device drivers with NASM
  2006-03-13 16:56 ` Frank Kotler
@ 2006-03-13 17:38   ` ALberto Andres
  0 siblings, 0 replies; 3+ messages in thread
From: ALberto Andres @ 2006-03-13 17:38 UTC (permalink / raw)
  To: fbkotler; +Cc: linux-assembly




>From: Frank Kotler <fbkotler@comcast.net>
>To: ALberto Andres <betorumbero@hotmail.com>
>CC: linux-assembly@vger.kernel.org
>Subject: Re: Writing Linux Device drivers with NASM
>Date: Mon, 13 Mar 2006 11:56:27 -0500
>
>ALberto Andres wrote:
>>Hi everybody, I'm writing a guide about device drivers in assembly under 
>>linux. I'm using NASM.  If anybody is interested here is the URL:
>>
>>http://albertoandreotti.5000megs.com/
>
>Great, Alberto! Couple thing seems strange to me. I don't know anything 
>about device drivers, so perhaps it really *is* that strange...
>
>You say:
>
>    2.      Stack cleanup is performed by the called function.
>    3.      Function name is decorated by prepending an underscore 
>character
>
>But that doesn't seem to be what you show...
>
>And... your strings have got CRs in 'em. Is that normal/required for device 
>drivers?
>
>I'm sure I'll have more questions... Great resource. Thanks!
>
>Best,
>Frank
>

I think you are talking about the call to the printk function. The string 
has a line feedback and carry return and a NULL (number 0) at the end. The 
format of the string is the same as the required for printf. The first two 
numbers are printed by printk and the zero indicates the end of the 
string(the convention followed by C strings).

Thanks for your interest.

_________________________________________________________________
Descubre la descarga digital con MSN Music. Más de un millón de canciones. 
http://music.msn.es/


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-03-13 17:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-13 15:45 Writing Linux Device drivers with NASM ALberto Andres
2006-03-13 16:56 ` Frank Kotler
2006-03-13 17:38   ` ALberto Andres

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.