sbusfb problems (and a patch)

D. Schwingel (nop@blue.netnation.com)
Thu, 8 Oct 1998 12:29:48 -0700 (PDT)


This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.

--0-641732159-907874988=:31447
Content-Type: TEXT/PLAIN; charset=US-ASCII

I was just trying 2.1.125 (from vger) on my sparc (ss2, cg6 fb), and found
several problems. Only one process was allowed to open the framebuffer
device at a time, and mmaping it causes a lockup at line 256 in sbusfb.c.
If I comment out that line (which looks like it is intended to turn off
the text cursor), there is no crash, but writing to the mmap'd area has no
visible result. (Seeking around in /dev/fb0 and writing works fine,
btw). I don't know if sbusfb_mmap ever worked, so I'm not sure where to
start in trying to fix it.. I've attached a patch for the sbusfb_{open,close} problem.

--0-641732159-907874988=:31447
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="sbusfb.diff"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.02A.9810081229480.31447@blue.netnation.com>
Content-Description:
Content-Disposition: attachment; filename="sbusfb.diff"

LS0tIGxpbnV4Lm9sZC9kcml2ZXJzL3ZpZGVvL3NidXNmYi5jCVNhdCBPY3Qg
IDMgMTY6MTI6MzcgMTk5OA0KKysrIGxpbnV4L2RyaXZlcnMvdmlkZW8vc2J1
c2ZiLmMJVGh1IE9jdCAgOCAxMjowODozOSAxOTk4DQpAQCAtMTI4LDkgKzEy
OCw3IEBADQogCXN0cnVjdCBmYl9pbmZvX3NidXNmYiAqZmIgPSBzYnVzZmJp
bmZvKGluZm8pOw0KIAkNCiAJaWYgKHVzZXIpIHsNCi0JCWlmIChmYi0+b3Bl
bikgcmV0dXJuIC1FQlVTWTsNCi0JCWZiLT5tbWFwZWQgPSAwOw0KLQkJZmIt
Pm9wZW4gPSAxOw0KKwkJZmItPm9wZW4rKzsNCiAJCWZiLT52dGNvbnNvbGUg
PSAtMTsNCiAJfSBlbHNlDQogCQlmYi0+Y29uc29sZWNudCsrOw0KQEAgLTE1
Miw3ICsxNTAsNyBAQA0KIAkJfQ0KIAkJaWYgKGZiLT5yZXNldCkNCiAJCQlm
Yi0+cmVzZXQoZmIpOw0KLQkJZmItPm9wZW4gPSAwOw0KKwkJZmItPm9wZW4t
LTsNCiAJfSBlbHNlDQogCQlmYi0+Y29uc29sZWNudC0tOw0KIAlNT0RfREVD
X1VTRV9DT1VOVDsNCg==
--0-641732159-907874988=:31447--

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/