CVS log for src/sys/arch/arm/s3c2xx0/s3c24x0_lcd.c

Up to [cvs.NetBSD.org] / src / sys / arch / arm / s3c2xx0

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

fix various typos in comments and log messages, mainly s/hight/high/
s/hight/height/ and removing double m in time(ing).

Sync w/ HEAD.

malloc(9) -> kmem(9)

Mostly merge changes from HEAD upto 20200411

in many device attach paths, allocate memory with M_WAITOK instead of M_NOWAIT
and remove code to handle failures that can no longer happen.

Sync with HEAD

Sync with HEAD

Resolve a couple of conflicts (result of the uimin/uimax changes)

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int.  The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER!  Some subsystems have

	#define min(a, b)	((a) < (b) ? (a) : (b))
	#define max(a, b)	((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX.  Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate.  But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all.  (Who knows, maybe in some cases integer
truncation is actually intended!)

update from HEAD

Remove dead returns:

	return VAR/func(XX);
	return VAR;

The latter is never reached. Sent on tech-kern@, no disagreement.

Rebase to HEAD as of a few days ago.

sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs.  ("Protocol error: too many arguments")

sync with head

Delete unused variables for new gcc.

Resync to 2012-11-19 00:00:00 UTC

sync with head

split device_t/softc for all remaining drivers.
replace "struct device *" with "device_t".
use device_xname(), device_unit(), etc.

sync with head

merge to -current.

Add FriendlyARM Mini2440 support.
- new code for Samsung S3C2440 SoC.
- update for other S3C2xx0.
This port was done by Paul Fleischer.

adjust wsfont_find()

#include <sys/bus.h> instead of <machine/bus.h>.

sync with head

sync with HEAD

Sync with HEAD

Sync with HEAD.

Sync with HEAD.

Sync with head.

__FUNCTION__ -> __func__

sync with head.

Sync with HEAD.

Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

sync with head

sync with head.

Merge 2006-05-24 NetBSD-current into the "peter-altq" branch.

sync with head.

Sync with head.

sync with head - hopefully this will work

Add missing parameter to s3c24x0_lcd_{ioctl,mmap} functions (after the
change in wscons that modified their signature) to let this build again.
Pointed out by he@.

merge ktrace-lwp.

Sync with HEAD. Here we go again...

Fix -Wcast-qual by sprinkling some consts, and remove named
parameters from a function prototype to avoid shadowing.
Also fix a couple of other shadowing problems.

Adapt to branch.

Fix the sync with head I botched.

Sync with HEAD.

Sync with HEAD

file s3c24x0_lcd.c was added on branch ktrace-lwp on 2004-08-03 10:32:50 +0000

Support S3C24X0's on-chip LCD controller.

lcd driver can be configured with or without wsdisplay.
With wsdisplay, it supports text mode using rasops in 8bpp or 16bpp.
Without it, users only can mmap(2) the framebuffer.

XXX: 1-, 2-, 4-, or 24- bpp mode is not supported yet.
XXX: S3C24x0's LCD controller can have virtual screen which is bigger
     than actual LCD panel. Our wsdisplay framework doesn't have
     features to utilize it.