Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
linux-davinci
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Redmine
Redmine
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Metrics
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
linux
linux-davinci
Commits
eef69e3c
Commit
eef69e3c
authored
Oct 27, 2005
by
Paul Mackerras
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
powerpc: remove duplicate screen_info from setup_32.c
Signed-off-by:
Paul Mackerras
<
paulus@samba.org
>
parent
4b24b01c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
15 deletions
+0
-15
arch/powerpc/kernel/setup_32.c
arch/powerpc/kernel/setup_32.c
+0
-15
No files found.
arch/powerpc/kernel/setup_32.c
View file @
eef69e3c
...
...
@@ -94,21 +94,6 @@ int dcache_bsize;
int
icache_bsize
;
int
ucache_bsize
;
#if defined(CONFIG_VGA_CONSOLE) || defined(CONFIG_FB_VGA16) || \
defined(CONFIG_FB_VGA16_MODULE) || defined(CONFIG_FB_VESA)
struct
screen_info
screen_info
=
{
0
,
25
,
/* orig-x, orig-y */
0
,
/* unused */
0
,
/* orig-video-page */
0
,
/* orig-video-mode */
80
,
/* orig-video-cols */
0
,
0
,
0
,
/* ega_ax, ega_bx, ega_cx */
25
,
/* orig-video-lines */
1
,
/* orig-video-isVGA */
16
/* orig-video-points */
};
#endif
/* CONFIG_VGA_CONSOLE || CONFIG_FB_VGA16 || CONFIG_FB_VESA */
/*
* We're called here very early in the boot. We determine the machine
* type and call the appropriate low-level setup functions.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment