From: Robin Murphy <robin.murphy@arm.com>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
Christoph Hellwig <hch@lst.de>
Cc: linux-arch@vger.kernel.org, darren@stevens-zone.net,
rtd2@xtra.co.nz,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
paulus@samba.org, mad skateman <madskateman@gmail.com>,
"contact@a-eon.com" <contact@a-eon.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
nsaenzjulienne@suse.de
Subject: Re: Bug 205201 - Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M
Date: Thu, 21 Nov 2019 13:33:52 +0000 [thread overview]
Message-ID: <d0252d29-7a03-20e1-ccd7-e12d906e4bdf@arm.com> (raw)
In-Reply-To: <6eec5c42-019c-a988-fc2a-cb804194683d@xenosoft.de>
On 21/11/2019 12:21 pm, Christian Zigotzky wrote:
> On 21 November 2019 at 01:16 pm, Christian Zigotzky wrote:
>> On 21 November 2019 at 08:29 am, Christoph Hellwig wrote:
>>> On Sat, Nov 16, 2019 at 08:06:05AM +0100, Christian Zigotzky wrote:
>>>> /*
>>>> * DMA addressing mode.
>>>> *
>>>> * 0 : 32 bit addressing for all chips.
>>>> * 1 : 40 bit addressing when supported by chip.
>>>> * 2 : 64 bit addressing when supported by chip,
>>>> * limited to 16 segments of 4 GB -> 64 GB max.
>>>> */
>>>> #define SYM_CONF_DMA_ADDRESSING_MODE
>>>> CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
>>>>
>>>> Cyrus config:
>>>>
>>>> CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
>>>>
>>>> I will configure “0 : 32 bit addressing for all chips” for the RC8.
>>>> Maybe this is the solution.
>>> 0 means you are going to do bounce buffering a lot, which seems
>>> generally like a bad idea.
>>>
>>> But why are we talking about the sym53c8xx driver now? The last issue
>>> you reported was about video4linux allocations.
>>>
>> Both drivers have the same problem. They don't work if we have more
>> than 3.5GB RAM. I try to find a solution until you have a good
>> solution. I have already a solution for V4L but I still need one for
>> the sym53c8xx driver.
> OK, you mean that "0" is a bad idea but maybe it works until you have a
> solution. ;-)
Is this on the same machine with the funny non-power-of-two bus_dma_mask
as your other report? If so, does Nicolas' latest patch[1] help at all?
Robin.
[1]
https://lore.kernel.org/linux-iommu/20191121092646.8449-1-nsaenzjulienne@suse.de/T/#u
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-11-21 13:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F1EBB706-73DF-430E-9020-C214EC8ED5DA@xenosoft.de>
2019-11-21 7:29 ` Bug 205201 - Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M Christoph Hellwig
2019-11-21 12:16 ` Christian Zigotzky
2019-11-21 12:21 ` Christian Zigotzky
2019-11-21 13:33 ` Robin Murphy [this message]
2019-11-21 16:34 ` Christian Zigotzky
2019-11-21 18:02 ` Christoph Hellwig
2019-11-21 18:21 ` Christian Zigotzky
2019-11-23 11:42 ` Christian Zigotzky
2019-11-25 7:39 ` Christoph Hellwig
2019-11-25 9:32 ` Mike Rapoport
2019-11-25 16:38 ` Christian Zigotzky
2019-11-26 11:57 ` Christian Zigotzky
2019-11-25 16:36 ` Christian Zigotzky
2019-11-26 11:26 ` Christian Zigotzky
2019-11-26 16:40 ` Christoph Hellwig
2019-11-27 6:56 ` Mike Rapoport
2019-11-27 8:53 ` Christoph Hellwig
2019-11-27 15:14 ` Christian Zigotzky
2019-12-04 8:56 ` Christoph Hellwig
2019-12-04 12:22 ` Christian Zigotzky
2020-01-10 7:10 ` Christian Zigotzky
2020-01-15 15:18 ` Christoph Hellwig
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=d0252d29-7a03-20e1-ccd7-e12d906e4bdf@arm.com \
--to=robin.murphy@arm.com \
--cc=benh@kernel.crashing.org \
--cc=chzigotzky@xenosoft.de \
--cc=contact@a-eon.com \
--cc=darren@stevens-zone.net \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=nsaenzjulienne@suse.de \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=rtd2@xtra.co.nz \
/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).