I can't verify either way, but I just thought about this for a second, and then read up on some doc's.
It's logical that it uses CoS to classify which queue it should enter, and CoS can only be introduced in ISL/802.1Q frames (and then implied internally in the switch of course). This logic is deducted from this being in fact done in hardware at the outer point of the switch, and the queue is there specifically enable the switch to receive packets and process them before forwarding.
The only thing you can do is set a default CoS value for the access-port. Then every packet could be put in the priority-queue.. but that wouldn't give you any more advantage..
So in conclusion: To use the different queues, you need differing CoS fields. To achieve different CoS fields, you need a trunk-port (and it to be set as "trusted").