Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

solved issue of mirroring screen after rotation. #1270

Closed
wants to merge 1 commit into from

Conversation

sphonala
Copy link

changed init code for rotation & new tft voltage problem.

@popcornmix
Copy link
Collaborator

We'll need more information on the problem and what this does.

Really this is an upstream file and the patch should be submitted upstream:
https://www.kernel.org/doc/Documentation/SubmittingPatches

I can't judge whether this is a safe change and won't cause problems for other users.
Once accepted upstream we can pull the change in.

Ping @notro who may know about this.

@sphonala
Copy link
Author

@notro, we have solved issue of 90 degree rotation for tinylcd 3.5 tft and voltage problems for new tinylcd tft's. the present init code for fb_tinylcd.c having an issue of 90 degree rotation, image showing its mirror after 90 degree rotation and also solved the voltage issue for new tft's with changing write_reg(par, 0xC1, 0x45, 0x07); to write_reg(par, 0xC1, 0x01, 0x01);
thanks.

@tinylcd
Copy link

tinylcd commented Jan 27, 2016

@notro commit this changes @sphonala to fb_tinylcd.c

@notro
Copy link
Contributor

notro commented Jan 27, 2016

fbtft is practically dead now.
The fbdev maintainer won't accept any new fbdev drivers: No more new fbdev drivers, please, so it can't be moved out of staging.
And Greg Kroah-Hartman (staging maintainer) didn't include any fbtft patches in the [GIT PULL] Staging driver patches for 4.5-rc1 change set.
This means that at some point it will be deleted, since staging is a temporary place for drivers to stay while they're cleaned up for inclusion in their proper place.

So there's no point in sending fbtft patches. Bug fixes might get in, but this seems to be a new display.

I have been working on and off on a DRM version of fbtft and I have a hack with one display working (sort of), but it's still some work to be done before I can post some patches for review.
This is my work so far: https://github.com/notro/tinydrm

@notro
Copy link
Contributor

notro commented Jan 27, 2016

Notify some more people about the current fbtft status: @ladyada @awatterott @mwilliams03

@ladyada
Copy link

ladyada commented Jan 27, 2016

ok thanks for the notice! hopefully the raspi fork can keep it in?

@Ferroin
Copy link
Contributor

Ferroin commented Jan 27, 2016

The intent is to get a rewrite using the DRM (Direct Rendering Manager) framework pushed upstream. Personally, I don't think it's likely that fbtft will be removed completely upstream until that happens, as the intent to eventually rewrite it using DRM has been stated on the mailing list.

@tinylcd
Copy link

tinylcd commented Jan 28, 2016

sad to know about "The fbdev maintainer won't accept any new fbdev drivers", hopefully the raspi fork can keep it in.
@notro Bug fixes might get in, but this seems to be a new display.
by these changes, voltage & rotation issues are fixed. these changes are now work on both new & old set of displays.

@notro
Copy link
Contributor

notro commented Jan 28, 2016

As @Ferroin says, if I can come up with a drm version in a reasonable time, fbtft won't go away before there's an alternative.
But that's just part of the story, because even if I make an alternative "library" solution, the individual displays have to be ported/supported. It isn't difficult to do, but it's takes time to do the testing and prepare patches. It's unlikely that I will do this even for all the displays I got myself. At least not in the required timeframe. Hence the heads up for some of the businesses that use these drivers. There's no problem yet, but it might be.

@tinylcd
Ok, if marked as a bug fix it should probably be accepted. However I can't do it.

@ladyada
Copy link

ladyada commented Jan 28, 2016

@notro np for the displays i have access to: HX5378D, ILI934x, SSDxxxx OLEDs, ST7735, etc. i've already done the code on an Arduino, so no biggie for me to re-port them again :)
without putting any pressure on you - do you have some ETA on when a DRM version may be available for first test? if not, do you mind pinging me when there's something to test?

@notro
Copy link
Contributor

notro commented Jan 29, 2016

@ladyada

do you have some ETA on when a DRM version may be available for first test?

No. I have worked on and off with this for over a year now, but this time around I plan to keep going until I have sent an RFC patchset for review.
The intention is to get some early feedback to see if I'm heading in the right direction.

if not, do you mind pinging me when there's something to test?

Sure.

I will also post updates in this thread: notro/tinydrm#2

@Ruffio
Copy link

Ruffio commented Aug 17, 2016

This PR is pointing to 4.1.y, is this ever going to be merged?

@popcornmix
Copy link
Collaborator

No would need to be resubmitted to 4.4 tree if still desired, although in general we are reluctant to keep patches to upstream code in this tree (we'd prefer the changes went upstream).

@popcornmix popcornmix closed this Aug 29, 2016
@js290 js290 mentioned this pull request Jan 12, 2020
popcornmix pushed a commit that referenced this pull request Dec 22, 2021
Fix up unprivileged test case results for 'Dest pointer in r0' verifier tests
given they now need to reject R0 containing a pointer value, and add a couple
of new related ones with 32bit cmpxchg as well.

  root@foo:~/bpf/tools/testing/selftests/bpf# ./test_verifier
  #0/u invalid and of negative number OK
  #0/p invalid and of negative number OK
  [...]
  #1268/p XDP pkt read, pkt_meta' <= pkt_data, bad access 1 OK
  #1269/p XDP pkt read, pkt_meta' <= pkt_data, bad access 2 OK
  #1270/p XDP pkt read, pkt_data <= pkt_meta', good access OK
  #1271/p XDP pkt read, pkt_data <= pkt_meta', bad access 1 OK
  #1272/p XDP pkt read, pkt_data <= pkt_meta', bad access 2 OK
  Summary: 1900 PASSED, 0 SKIPPED, 0 FAILED

Acked-by: Brendan Jackman <jackmanb@google.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
popcornmix pushed a commit that referenced this pull request Dec 22, 2021
commit e523102 upstream.

Fix up unprivileged test case results for 'Dest pointer in r0' verifier tests
given they now need to reject R0 containing a pointer value, and add a couple
of new related ones with 32bit cmpxchg as well.

  root@foo:~/bpf/tools/testing/selftests/bpf# ./test_verifier
  #0/u invalid and of negative number OK
  #0/p invalid and of negative number OK
  [...]
  #1268/p XDP pkt read, pkt_meta' <= pkt_data, bad access 1 OK
  #1269/p XDP pkt read, pkt_meta' <= pkt_data, bad access 2 OK
  #1270/p XDP pkt read, pkt_data <= pkt_meta', good access OK
  #1271/p XDP pkt read, pkt_data <= pkt_meta', bad access 1 OK
  #1272/p XDP pkt read, pkt_data <= pkt_meta', bad access 2 OK
  Summary: 1900 PASSED, 0 SKIPPED, 0 FAILED

Acked-by: Brendan Jackman <jackmanb@google.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants