mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Dave Penkler <dpenkler@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [GIT PULL] Staging driver changes for 6.13-rc1
Date: Mon, 2 Dec 2024 09:02:25 -0800	[thread overview]
Message-ID: <c92efa1b-7353-4e54-982d-9d861fe36e68@roeck-us.net> (raw)
In-Reply-To: <Z03TqThAOa29MEjD@egonzo>

On 12/2/24 07:35, Dave Penkler wrote:
> On Mon, Dec 02, 2024 at 06:52:28AM -0800, Guenter Roeck wrote:
>> On Mon, Dec 02, 2024 at 10:50:07AM +0100, Dave Penkler wrote:
>> [ ... ]
>>> That is weird: the type of resource.start is resource_size_t which resolves to u32 via phys_addr_t on i386 which should be the same size as void *
>>> For compile check purposes simply changing iobase type to phys_addr_t the following error message appears:
>>>
>>> drivers/staging/gpib/ines/ines_gpib.c: In function 'ines_common_pci_attach':
>>> drivers/staging/gpib/ines/ines_gpib.c:783:28: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
>>>    783 |         nec_priv->iobase = (void *)(pci_resource_start(ines_priv->pci_device,
>>>        |                            ^
>>> drivers/staging/gpib/ines/ines_gpib.c:783:26: error: assignment to 'phys_addr_t' {aka 'long long unsigned int'} from 'void *' makes integer from pointer without a cast [-Wint-conversion]
>>>    783 |         nec_priv->iobase = (void *)(pci_resource_start(ines_priv->pci_device,
>>>        |                          ^
>>>
>>> It would seem that for some reason phys_addr_t resolves to long long unsigned int
>>
>> Check out CONFIG_X86_PAE, which adds 64-bit physical address support to
>> 32-bit x86 images. Pointers are still 32 bit in that mode, though.
>>
>> Guenter
> OK thanks. I will submit a patch to use ioremap.
> -Dave

FWIW, I applied the following patch (hack) to my fixes branch to get around
the build problem.

Guenter

---
diff --git a/drivers/staging/gpib/Kconfig b/drivers/staging/gpib/Kconfig
index 9ee432316465..a9fe2920d5c0 100644
--- a/drivers/staging/gpib/Kconfig
+++ b/drivers/staging/gpib/Kconfig
@@ -1,6 +1,7 @@
  # SPDX-License-Identifier: GPL-2.0
  menuconfig GPIB
         tristate "Linux GPIB drivers"
+       depends on !X86_PAE
         help
           Enable support for GPIB cards and dongles for Linux.  GPIB
           is the General Purpose Interface Bus which conforms to the


      reply	other threads:[~2024-12-02 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29  4:27 Greg KH
2024-11-29 20:30 ` pr-tracker-bot
2024-11-30 16:10 ` Guenter Roeck
2024-11-30 16:15   ` Greg KH
2024-11-30 17:07     ` Guenter Roeck
2024-12-02  9:50       ` Dave Penkler
2024-12-02 14:52         ` Guenter Roeck
2024-12-02 15:35           ` Dave Penkler
2024-12-02 17:02             ` Guenter Roeck [this message]

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=c92efa1b-7353-4e54-982d-9d861fe36e68@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=dpenkler@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®