From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] How to add djet500' driver to gs?
Date: Tue, 19 Jan 2010 07:14:41 -0800 [thread overview]
Message-ID: <dd6fe68a1001190714k4828926bh306ecfae6b3d0c5a@mail.gmail.com> (raw)
In-Reply-To: <cd6983821001181930p42e89a01u86c9527a1fa3279d@mail.gmail.com>
> I'm currently trying to get my HP Deskjet 500 (/dev/lptr1data) working
> in native Plan 9. Using 'lp -d hpdeskjet file' the printer works
> basically; it takes in a sheet and starts printing.
> But it prints only weird symbols and mishandles newlines etc..
>
> I did a little research and found that there is a 'djet500' driver
> (see /sys/src/cmd/gs/src/gdevdjet.c) available for gs but it is not
> included in the stock gs binary according to the output of 'gs -?'. I
> added the djet500 driver to /sys/src/cmd/gs/mkfile and run 'mk
> fake-make' and then 'mk install' as described in the mkfile.
>
> It builds with no error messages but the output of the freshly
> compiled 'gs -?' still doesn't show the new djet500 driver.
>
> What is the right/working procedure to add drivers to gs?
It looks like the mkfile has a small bug in that
src/plan9.mak, which fake-make works from,
doesn't depend on mkfile itself, so mk didn't regenerate
it after you changed the mkfile. You can check this
theory by doing
cd /sys/src/cmd/gs
grep '^DEVICE_DEVS=' src/plan9.mak | grep djet500
I bet grep will not find anything.
Assuming that's the case, you should be able to
get the driver added by running
cd /sys/src/cmd/gs
rm src/plan9.mak # works around bug
mk fake-make
mk install
Good luck.
Russ
next prev parent reply other threads:[~2010-01-19 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 3:30 Frederik Caulier
2010-01-19 15:14 ` Russ Cox [this message]
2010-01-20 2:20 ` Frederik Caulier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd6fe68a1001190714k4828926bh306ecfae6b3d0c5a@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).