All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: Boaz Harrosh <bharrosh@panasas.com>, Jiri Slaby <jslaby@suse.cz>,
	fischer@linux-buechse.de, linux-scsi@vger.kernel.org
Subject: Re: Why is AHA152X_CS !64BIT?
Date: Tue, 07 Sep 2010 14:48:16 -0700	[thread overview]
Message-ID: <4C86B320.8090709@oracle.com> (raw)
In-Reply-To: <4C86B1A4.8030308@oracle.com>

On 09/07/10 14:41, Randy Dunlap wrote:
> On 09/07/10 14:12, Konrad Rzeszutek Wilk wrote:
>> On Monday 30 August 2010 07:13:17 Boaz Harrosh wrote:
>>> On 08/23/2010 10:59 PM, Jiri Slaby wrote:
>>>> Hi,
>>>>
>>>> I see that the aha152x driver for pcmcia is marked as unsupported on
>>>> 64bit. But I also see a patch [1] which removes the restriction based on
>>>> user's testing in bugzilla [2].
>>>>
>>>> Is there a reason why it would have to be marked as !64BIT? I'm asking
>>>> because there is an opensuse user with this card who updated to 64-bit
>>>> distro and lost this driver thereafter.
>>>>
>>>> [1] http://kerneltrap.org/mailarchive/linux-scsi/2010/3/6/6832393
>>>> [2] https://bugzilla.kernel.org/show_bug.cgi?id=14333
>>>>
>>>> thanks,
>>>
>>> If memory serves correctly, it might be that you need more then 4 Gbyte
>>> of memory installed to exercise the bug, something about IO bouncing
>>> addresses > 4G.
>>
>> If the machine is using SWIOTLB, then the bounce buffer would be activated. By 
>> default if your machine has more than 4GB compiled under x86_64 the SWIOTLB 
>> is turned on - but if you have an Intel/AMD IOMMU it gets turned off. Which 
>> is OK as the Intel/AMD IOMMUs would handle the 4GB restricted devices. So as 
>> long as the driver has pci_dma_mask_set.
>>
>> Looking at the git gui blame tool history, the reason that was added was 
>> for 'allow drivers to be built non-modular'.
> 
> 023ae619 (Robert P. J. Day  2007-03-26 16:06:45 -0400 14) 	depends on !64BIT
> 
> That commit just removed the "depends on m" part:
> 
> -	depends on m && !64BIT
> +	depends on !64BIT
> 
> 
>> So, does this driver build if you make it non-modular?
> 
> It shouldn't since it still depends on !64BIT.
> 
> I expect someone thought or had evidence that the driver was not 64-bit clean.
> 
> Is the bitkeeper kernel repo still visible somewhere?
> Looks like we would need to look at it for patch history that far back.
> 

http://linux.bkbits.net:8080/linux-2.6/?PAGE=cset&REV=3fe0bc41KO89ooP68UcrHEMVVAfDnw

but it doesn't quite make sense to me.  Sure, no ISA on x86_64, but that does not
mean no PCMCIA on x86_64.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-09-07 21:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 19:59 Why is AHA152X_CS !64BIT? Jiri Slaby
2010-08-30 11:13 ` Boaz Harrosh
2010-09-07 21:12   ` Konrad Rzeszutek Wilk
2010-09-07 21:41     ` Randy Dunlap
2010-09-07 21:48       ` Randy Dunlap [this message]
2010-09-07 22:10         ` James Bottomley
2010-09-07 22:16           ` Jiri Slaby
2010-09-09 20:01             ` =?unknown-8bit?B?SvxyZ2VuIEUu?= Fischer
2010-09-07 22:10         ` Jiri Slaby
2010-09-08  6:05           ` Andi Kleen
2010-09-08 15:30             ` James Bottomley
2010-09-09  6:50               ` Andi Kleen
2010-09-24 19:55                 ` Jiri Slaby

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=4C86B320.8090709@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=bharrosh@panasas.com \
    --cc=fischer@linux-buechse.de \
    --cc=jslaby@suse.cz \
    --cc=konrad@darnok.org \
    --cc=linux-scsi@vger.kernel.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 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.