linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Tobias Baumann <017623705678@o2online.de>
Cc: hdegoede@redhat.com, Larry.Finger@lwfinger.net,
	gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: RTL8723BS driver doesn't work for,me but I can help testing
Date: Mon, 18 May 2020 00:31:59 +0200	[thread overview]
Message-ID: <CAFBinCBukGbzgO-Y1dCRYXZHhX2PcSEQQ_XvhHqLcnw0fGDP8w@mail.gmail.com> (raw)
In-Reply-To: <8cbbf90c-54ba-8fa3-3386-022c9c997a20@o2online.de>

Hi Tobias,

On Sun, May 17, 2020 at 11:05 PM Tobias Baumann
<017623705678@o2online.de> wrote:
>
> hi martin
>
> sorry for cc -problem it was my fault in thunderbird
>
> thanks for dtb file but this file has problem kernel stop with
>
> [    6.122092] mmc0: new high speed SDIO card at address 0001
> [   35.804258] VCCK: disabling
> [   35.808781] platform pwmleds: deferred probe pending
> [   35.812625] platform sound: deferred probe pending
pwmleds was also there in your last dmesg
please ignore the sound part, I haven't tested it on that particular
board in a while


> [  215.804295] random: crng init done
>
> (last time deferred probe was gcc problem )
>
> please can you provide me with dts file and i complile at my linux box
> or maybe only the change line and i use the dtb from image and edit the
> lines like the usb patch
you can get all my patches from here: [0]
as always: some of them are not even in linux-next yet and there's a
reason for that ;-)
I have changed the GPIO_ACTIVE_* polarity for the two GPIOs in the
sdio_pwrseq node if you want to do that by yourself.


Best regards,
Martin


[0] https://github.com/xdarklight/linux/tree/meson-mx-integration-5.8-20200517

  reply	other threads:[~2020-05-17 22:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  8:57 RTL8723BS driver doesn't work for,me but I can help testing Tobias Baumann
2020-05-16 18:03 ` Martin Blumenstingl
     [not found]   ` <22af498b-44a0-ced3-86f3-114427a73910@o2online.de>
     [not found]     ` <CAFBinCCGAkhPCwOW=mAvsV2qdixq8Gf8yQw1gYErHpz7KmuAZg@mail.gmail.com>
     [not found]       ` <5de6db87-a71f-d14c-390d-b0caeab5d650@o2online.de>
     [not found]         ` <CAFBinCDB9c2uMRXO9DKSX4hC7EBgnRfBa+BM5-VdEPZeieKn_w@mail.gmail.com>
     [not found]           ` <813dfc08-f13a-dcac-0bd9-821d188bba08@o2online.de>
2020-05-17 20:28             ` Martin Blumenstingl
2020-05-17 21:04               ` Tobias Baumann
2020-05-17 22:31                 ` Martin Blumenstingl [this message]
2020-05-18  5:59                   ` Tobias Baumann
2020-05-18 20:37                     ` Martin Blumenstingl
2020-05-19  6:21                       ` Tobias Baumann
2020-05-19 20:16                         ` Martin Blumenstingl
     [not found]                           ` <fb9d8d57-2958-4023-2a95-af240714d5df@o2online.de>
2020-05-23  7:47                             ` Tobias Baumann
2020-05-26 20:13                             ` Martin Blumenstingl

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=CAFBinCBukGbzgO-Y1dCRYXZHhX2PcSEQQ_XvhHqLcnw0fGDP8w@mail.gmail.com \
    --to=martin.blumenstingl@googlemail.com \
    --cc=017623705678@o2online.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@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 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).