Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
U
u-boot-2015.04
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
vesta
u-boot-2015.04
Commits
6e24a1eb
Commit
6e24a1eb
authored
16 years ago
by
Remy Bohmer
Committed by
Wolfgang Denk
16 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Add missing device types to dev_print() in part.c
Signed-off-by:
Remy Bohmer
<
linux@bohmer.net
>
parent
5fdc215f
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
disk/part.c
+9
-1
9 additions, 1 deletion
disk/part.c
with
9 additions
and
1 deletion
disk/part.c
+
9
−
1
View file @
6e24a1eb
...
...
@@ -117,6 +117,7 @@ void dev_print (block_dev_desc_t *dev_desc)
dev_desc
->
product
,
dev_desc
->
revision
);
break
;
case
IF_TYPE_ATAPI
:
case
IF_TYPE_IDE
:
case
IF_TYPE_SATA
:
printf
(
"Model: %s Firm: %s Ser#: %s
\n
"
,
...
...
@@ -124,15 +125,22 @@ void dev_print (block_dev_desc_t *dev_desc)
dev_desc
->
revision
,
dev_desc
->
product
);
break
;
case
IF_TYPE_SD
:
case
IF_TYPE_MMC
:
case
IF_TYPE_USB
:
printf
(
"Vendor: %s Rev: %s Prod: %s
\n
"
,
dev_desc
->
vendor
,
dev_desc
->
revision
,
dev_desc
->
product
);
break
;
case
IF_TYPE_DOC
:
puts
(
"device type DOC
\n
"
);
return
;
case
IF_TYPE_UNKNOWN
:
puts
(
"device type unknown
\n
"
);
return
;
default:
p
uts
(
"not available
\n
"
);
p
rintf
(
"Unhandled device type: %i
\n
"
,
dev_desc
->
if_type
);
return
;
}
puts
(
" Type: "
);
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment