All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fbdump: Make fbdump available only to x86/x86_64/arm architectures
Date: Wed, 14 Mar 2012 10:43:17 +0000	[thread overview]
Message-ID: <4F607645.1030603@imgtec.com> (raw)
In-Reply-To: <20120314113754.17f75aaf@skate>

On 03/14/2012 10:37 AM, Thomas Petazzoni wrote:

> Hello,
> 
> Le Wed, 14 Mar 2012 10:02:14 +0000,
> Markos Chandras <markos.chandras@imgtec.com> a ?crit :
> 
>> fbdump uses the ioperm() syscall which is only implemented in
>> x86/x86_64. The rest of the architectures map ioperm() to
>> sys_ni_syscall which is the default function for the unimplemented
>> syscalls. Moreover, ARM has its own ioperm() implementation
>> in uClibc.
> 
> Is ioperm() on ARM only available if uClibc is used, and not when glibc
> is used?
> 
>> diff --git a/package/fbdump/Config.in b/package/fbdump/Config.in
>> index fb4aee6..2f8040f 100644
>> --- a/package/fbdump/Config.in
>> +++ b/package/fbdump/Config.in
>> @@ -1,3 +1,4 @@
>> +if BR2_i386 || BR2_x86_64 || BR2_arm
>>  config BR2_PACKAGE_FBDUMP
>>  	bool "fbdump (Framebuffer Capture Tool)"
>>  	help
>> @@ -5,4 +6,4 @@ config BR2_PACKAGE_FBDUMP
>>  	  framebuffer  device and write them out as a PPM file. Currently,
>>  	  most packed-pixel framebuffer formats and the vga16 framebuffer
>>  	  are supported.
>> -
>> +endif
> 
> I would prefer:
> 
> config BR2_PACKAGE_FBDUMP
> 	bool "fbdump (Framebuffer Capture Tool)"
> 	depends on BR_i386 || BR2_x86_64 || BR2_arm
> 
> because that's what we do for all other packages.
> 
> Thomas


Hi Thomas,

Thanks for your suggestion. I fixed and resent my patch.

-- 
markos

  reply	other threads:[~2012-03-14 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 10:02 [Buildroot] [PATCH] fbdump: Make fbdump available only to x86/x86_64/arm architectures Markos Chandras
2012-03-14 10:37 ` Thomas Petazzoni
2012-03-14 10:43   ` Markos Chandras [this message]
2012-03-14 11:02     ` Thomas Petazzoni
2012-03-14 11:33       ` Markos Chandras
2012-03-14 11:48       ` Markos Chandras
2012-03-14 11:55         ` Thomas Petazzoni
2012-03-14 13:56           ` Markos Chandras
  -- strict thread matches above, loose matches on Subject: below --
2012-03-14 10:40 Markos Chandras

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=4F607645.1030603@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=buildroot@busybox.net \
    /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 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.