netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: maximilian attems <max@stro.at>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	David Miller <davem@davemloft.net>,
	mchan@broadcom.com, vda.linux@googlemail.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: bnx2 dirver's firmware images
Date: Wed, 19 Sep 2007 19:37:04 +0200	[thread overview]
Message-ID: <20070919173704.GA3115@uranus.ravnborg.org> (raw)
In-Reply-To: <20070919171841.GT19918@baikonur.stro.at>

Hi Maks.

On Wed, Sep 19, 2007 at 07:18:41PM +0200, maximilian attems wrote:
> On Wed, Sep 19, 2007 at 10:12:38AM -0700, H. Peter Anvin wrote:
> > 
> > Could you give a concrete example?
> > 
> > 	-hpa
> 
> max@dual:~/src/klibc$ touch usr/utils/mount_main.c
> max@dual:~/src/klibc$ make
>   KLIBCCC usr/utils/mount_main.o
>   KLIBCLD usr/utils/static/halt
>   LN      usr/utils/static/reboot
>   LN      usr/utils/static/poweroff
>   KLIBCLD usr/utils/shared/halt
>   LN      usr/utils/shared/reboot
>   LN      usr/utils/shared/poweroff
>   KLIBCLD usr/utils/static/chroot
>   KLIBCLD usr/utils/static/dd
>   <snipp>

I do not recall the details at the moment but I recall I had to
do this tradeoff for some reasons.
I do not say it is not fixable but when I did the static-y support
I recall I took a shortcut or two under the assumption that everything
build by klibc was anyway so simple that compiling a bit too much was no harm.

Too buried with other stuff right now.
But feel free to poke me in roughly a month and I will take a deeper look.

	Sam

  reply	other threads:[~2007-09-19 17:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200709181823.26429.vda.linux@googlemail.com>
2007-09-18 18:45 ` bnx2 dirver's firmware images Michael Chan
2007-09-18 17:55   ` Denys Vlasenko
2007-09-18 19:09     ` Michael Chan
2007-09-18 18:23   ` David Miller
2007-09-18 18:41     ` H. Peter Anvin
2007-09-18 19:20       ` David Miller
2007-09-18 19:27         ` H. Peter Anvin
2007-09-18 20:08           ` David Miller
2007-09-18 20:35             ` Sam Ravnborg
2007-09-18 20:40               ` H. Peter Anvin
2007-09-19 17:10               ` maximilian attems
2007-09-19 17:12                 ` H. Peter Anvin
2007-09-19 17:18                   ` maximilian attems
2007-09-19 17:37                     ` Sam Ravnborg [this message]
2007-09-18 20:05     ` Michael Chan
2007-09-18 19:21       ` David Miller
2007-09-18 21:30         ` Willy Tarreau
2007-09-18 21:31           ` David Miller
2007-09-18 21:37             ` Willy Tarreau
2007-09-18 23:14               ` Michael Chan
2007-09-19 13:40         ` Bill Davidsen
2007-09-19 16:09           ` David Miller
2007-09-19  8:30       ` Denys Vlasenko
2007-09-19 21:00         ` Michael Chan
2007-09-19 20:29           ` Denys Vlasenko
2007-09-19 21:43             ` Michael Chan
2007-09-20 14:49               ` Denys Vlasenko
2007-09-21  2:12                 ` Michael Chan
2007-09-19 16:33       ` maximilian attems
2007-09-19 16:38         ` David Miller
2007-09-19 16:51           ` maximilian attems

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070919173704.GA3115@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davem@davemloft.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=vda.linux@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).